Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support Strimzi Operator Deployment to K8s env + IPv6 #9184

Closed
wants to merge 1 commit into from

Conversation

rao2100
Copy link
Contributor

@rao2100 rao2100 commented Sep 30, 2023

Type of change

Enhancement

Description

While deploying cluster operator to K8s env configured with IPv6, we were stumped by the following errors.

2021-01-28 18:23:18 INFO  Main:60 - ClusterOperator 0.19.0 is starting 
2021-01-28 18:23:21 ERROR PlatformFeaturesAvailability:124 - Detection of Kubernetes version failed.
io.fabric8.kubernetes.client.KubernetesClientException: An error has occurred.
       at io.fabric8.kubernetes.client.KubernetesClientException.launderThrowable(KubernetesClientException.java:64) ~[io.fabric8.kubernetes-client-4.6.4.ja
r:?]
       at io.fabric8.kubernetes.client.KubernetesClientException.launderThrowable(KubernetesClientException.java:53) ~[io.fabric8.kubernetes-client-4.6.4.ja

Caused by: javax.net.ssl.SSLPeerUnverifiedException: Hostname fc11::1 not verified: 
   certificate: sha256/Vt4FXjXwAY2l7cffNShXdFLUQVnTw12pSsnv4WLdTdY=
   DN: CN=kube-apiserver
   subjectAltNames: [127.0.0.1, fc11:0:0:0:0:0:0:1, x270n01-vm01-ip6-oam, x270n01-vm01-ip6, x270n02-vm01-ip6-oam, x270n02-vm01-ip6, x270n03-vm01-ip6-oam, x2
70n03-vm01-ip6, localhost, kubernetes, kubernetes.default, kubernetes.default.svc, kubernetes.default.svc.cluster.local]
       at okhttp3.internal.connection.RealConnection.connectTls(RealConnection.java:334) ~[com.squareup.okhttp3.okhttp-3.12.6

Similar issue was reported by others in #4002; suggesting that "The workaround I used and verified is setting the KUBERNETES_MASTER to the actual Kubernetes master on the got through the kubectl cluster-info command."

We added the following environment variables in Helm chart and issue is resolved.

env:
  - name: KUBERNETES_MASTER
    value: https://[fc00:129:40:80::83]:6443
  - name: KUBERNETES_DISABLE_HOSTNAME_VERIFICATION
    value: "true"

The strimzi operator was able to deploy successfully after that.

$ k get pod -n odf
NAME                                        READY   STATUS    RESTARTS   AGE
strimzi-cluster-operator-7cb9d78f6f-pscmf   1/1     Running   0          126m

Checklist

  • Write tests
  • Make sure all tests pass
  • Update documentation
  • Check RBAC rights for Kubernetes / OpenShift roles
  • Try your changes from Pod inside your Kubernetes and OpenShift cluster, not just locally
  • Reference relevant issue(s) and close them after merging
  • Update CHANGELOG.md
  • Supply screenshots for visual changes, such as Grafana dashboards

@rao2100 rao2100 changed the title Disable hostname verification so that ipv6 can be configured Support Strimzi Operator Deployment to K8s env configured with IPv6 Sep 30, 2023
@rao2100 rao2100 changed the title Support Strimzi Operator Deployment to K8s env configured with IPv6 Support Strimzi Operator Deployment to K8s env + IPv6 Sep 30, 2023
Copy link
Member

@scholzj scholzj left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why does this need new options? You can configure these options using .Values.extraEnvs already.

@scholzj
Copy link
Member

scholzj commented Sep 30, 2023

This also likely works differently in the current Strimzi versions compared to Strimzi 0.19? OkHttp is not used anymore for example.

@scholzj
Copy link
Member

scholzj commented Oct 5, 2023

Triaged on the community call 5th October: This can be done using .Values.extraEnvs so this does not seem to be needed and can be closed.

@scholzj scholzj closed this Oct 5, 2023
@rao2100
Copy link
Contributor Author

rao2100 commented Oct 6, 2023

@scholzj Thank you , yeah this works for us, we have been porting the changes we did in 0.19.0 over all the while in our fork of the repo.

This pull request was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants