az connectedk8s delete fails as there is no proxy settings params available

[ezYakaEagle442]

• If the issue is to do with Azure CLI 2.0 in-particular, create an issue here at Azure/azure-cli

created with private-preview :

export REGISTRY=<registry-name> # example: example.registry.com 
export REGISTRY_USERNAME=<username> 
export REGISTRY_PASSWORD=<password> 

bash ./setuptestenv_arck8s.sh 


export HTTP_PROXY=<proxy-server-ip-address>:<port> 
export HTTPS_PROXY=<proxy-server-ip-address>:<port> 
export NO_PROXY=<cluster-apiserver-ip-address>:<port> 

az connectedk8s connect -n $azure_arc_ocp_cluster_name -g $poc_rg_name \ 
--distribution openshift --location francecentral \ 
--auto-upgrade false --agent-version 0.1.4149-private \ 
--registry-repository ${REGISTRY} --registry-username ${REGISTRY_USERNAME} --registry-password ${REGISTRY_PASSWORD} \ 
--proxy-https https://<proxy-server-ip-address>:<port> \ 
--proxy-http http://<proxy-server-ip-address>:<port> \ 
--proxy-skip-range <excludedIP>,<excludedCIDR> \ 
--proxy-cert <path-to-cert-file>

Extension name (the extension in question)

az connectedk8s delete 

has not as much parameters as the

az connectedk8s create 

Proxy Arguments
    --proxy-cert                   : Path to the certificate file for proxy.
    --proxy-http                   : Http proxy URL to be used.
    --proxy-https                  : Https proxy URL to be used.
    --proxy-skip-range             : List of URLs/CIDRs for which proxy should not to be used.

Description of issue (in as much detail as possible)

Env. : OpenShift OCP 4.6 on-prem

 az version

{
"azure-cli": "2.28.0",
"azure-cli-core": "2.28.0",
"azure-cli-telemetry": "1.0.6",
"extensions": {
"connectedk8s": "1.3.0",
"k8s-extension": "0.7.1",
"ml": "2.0.1a5"
}
}

---

[ezYakaEagle442]

@shashankbarsin @Bozhong68 @Zhong-J Could you please have a look Thank you, Steve

[ghost]

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @akashkeshari.

Issue Details

---

• If the issue is to do with Azure CLI 2.0 in-particular, create an issue here at Azure/azure-cli

created with private-preview :

export REGISTRY=<registry-name> # example: example.registry.com 
export REGISTRY_USERNAME=<username> 
export REGISTRY_PASSWORD=<password> 

bash ./setuptestenv_arck8s.sh 


export HTTP_PROXY=<proxy-server-ip-address>:<port> 
export HTTPS_PROXY=<proxy-server-ip-address>:<port> 
export NO_PROXY=<cluster-apiserver-ip-address>:<port> 

az connectedk8s connect -n $azure_arc_ocp_cluster_name -g $poc_rg_name \ 
--distribution openshift --location francecentral \ 
--auto-upgrade false --agent-version 0.1.4149-private \ 
--registry-repository ${REGISTRY} --registry-username ${REGISTRY_USERNAME} --registry-password ${REGISTRY_PASSWORD} \ 
--proxy-https https://<proxy-server-ip-address>:<port> \ 
--proxy-http http://<proxy-server-ip-address>:<port> \ 
--proxy-skip-range <excludedIP>,<excludedCIDR> \ 
--proxy-cert <path-to-cert-file>

Extension name (the extension in question)

az connectedk8s delete 

has not as much parameters as the

az connectedk8s create 

Proxy Arguments
    --proxy-cert                   : Path to the certificate file for proxy.
    --proxy-http                   : Http proxy URL to be used.
    --proxy-https                  : Https proxy URL to be used.
    --proxy-skip-range             : List of URLs/CIDRs for which proxy should not to be used.

Description of issue (in as much detail as possible)

Env. : OpenShift OCP 4.6 on-prem

 az version

{
"azure-cli": "2.28.0",
"azure-cli-core": "2.28.0",
"azure-cli-telemetry": "1.0.6",
"extensions": {
"connectedk8s": "1.3.0",
"k8s-extension": "0.7.1",
"ml": "2.0.1a5"
}
}

---

Author:	ezYakaEagle442
Assignees:	-
Labels:	Service Attention, needs-triage, Connected Kubernetes
Milestone:	-

[yonzhan]

route to service team

[zioalex]

Hi, I have the same problem with the connect command. Any follow-up on this?

These are the az cli versions:

az version
{
  "azure-cli": "2.36.0",
  "azure-cli-core": "2.36.0",
  "azure-cli-telemetry": "1.0.6",
  "extensions": {
    "azure-devops": "0.22.0",
    "connectedk8s": "1.2.8",
    "k8s-configuration": "1.5.1",
    "monitor-control-service": "0.2.0"
  }
}