-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
4.16.z
-
None
-
False
-
Description of problem:
When creating a hosted cluster and adding a proxy configuration as a day 2 post create change, the proxy configuration is never reconciled into the nodepool, despite the configuration change triggering a new node to rollout.
Example:
spec:
configuration:
proxy:
httpProxy: http://10.0.7.103:8080
httpsProxy: https://10.0.7.103:8080
trustedCA:
name: user-ca-bundle
If we add the below annotation to the management cluster proxy configuration, the hosted cluster reconciles the proxy config and you can see it correctly in the
metadata:
annotations:
hypershift.io/hosted-cluster-proxy-config: "true"
Node config after reconcile:
[core@ocp-wdc-lab-int-5-96a2d0a9-c2zl4 ~]$ cat /etc/mco/proxy.env # Proxy environment variables will be populated in this file. Properly # url encoded passwords with special characters will use '%<HEX><HEX>'. # Systemd requires that any % used in a password be represented as # %% in a unit file since % is a prefix for macros; this restriction does not # apply for environment files. Templates that need the proxy set should use # 'EnvironmentFile=/etc/mco/proxy.env'. HTTP_PROXY=http://proxyweb-server.com:80 HTTPS_PROXY=http://proxyweb-server.com:80 NO_PROXY=.cluster.local,.is.name.com,.local,.name.com,.svc,100.64.0.0/20,100.64.16.0/20,127.0.0.1,is.name.com,localhost,name.com
Additionally, if we change the proxy config, it does not get reconciled. You need to touch (ex: flip it false/true) the annotation and then it will reconcile the changes.
Version-Release number of selected component (if applicable):
4.16.18 - management and hosted cluster MCE 2.7
How reproducible:
Always
Steps to Reproduce:
1. Deploy hcp on virt with no proxy
hcp create cluster kubevirt --name ocp-lab-6 --base-domain paas.com --cores 6 --memory 64Gi --additional-network "name:default/ppcore-547" --attach-default-network false --cluster-cidr 100.64.0.0/20 --service-cidr 100.64.16.0/20 --network-type OVNKubernetes --node-pool-replicas 3 --ssh-key ~/deploy --pull-secret pull-secret.txt --release-image quay.io/openshift-release-dev/ocp-release:4.16.18-x86_64
2. Edit the HostedCluster and add the proxy config
3. New node gets bursted and created, but has no proxy config.
Actual results:
No proxy config
Expected results:
Valid proxy config
Additional info:
