Monday, 2021-08-02

airship-irc-bot<amir.boroufar> Thank you @bs782g @ratnopam.chakrabarti, I will update you06:59
airship-irc-bot<vetbijaya> Hi team, can I get some reviews on this PS related to plan status cmd https://review.opendev.org/c/airship/airshipctl/+/772890 Thank you in advance!14:37
airship-irc-bot<sidney.shiba> Hi team, I need somebody help?  While troubleshooting the `clusterctl-init-<cluster name>` execution I failed to determine how/where the `clusterctl` krm container gets the `cert-manager` manifests to apply. The reason is to determine if the `cert-manager` (`Deployment`) manifests include the `tolerations` to allow the `cert-manager` pods be deployed on the control plane nodes of the Target cluster.  In the CAPZ case, the15:11
airship-irc-bot`cert-manager` pods hang during the `clusterctl-init-target` phase run and blocks the rest of providers to be deployed.15:11
airship-irc-bot<sidney.shiba> For CAPZ, deploying CNI is different and now I see the issue. Will have to add the cert-manager manifests in the cni/calico-capz. Thanks @raliev for the help.15:36
airship-irc-bot<raliev> it is however possible to customize cert-manager installation during clusterctl init process. but for this there is need to make additional changes to our Clusterctl kind. let me know if you need such functionality, previously we didn’t have it, but if there is a case it is possible to implement15:39
airship-irc-bot<sidney.shiba> No need to change the code. I will create a new composite `infra-capz` so it stays consistent with other operators.15:40
airship-irc-bot<amir.boroufar> Hi guys, I am not able to initialize an ephemeral cluster anymore, I got this error:  v1alpha1.Clusterctl.InitOptions: v1alpha1.InitOptions.BootstrapProviders: []string: decode slice: expect [ or n, but found ", error found in #10 byte of ...|oviders":"kubeadm:v0|..., bigger context ...|"v0.4.1"}},"init-options":{"bootstrap-providers":"kubeadm:v0.3.7","control-plane-providers":"kubeadm|...16:10
airship-irc-bot<raliev> @amir.boroufar there was a small change in Clusterctl kind recently, providers now are not lists, but strings with comma separated versions: https://github.com/airshipit/airshipctl/blob/master/manifests/function/clusterctl/clusterctl.yaml#L8 please adjust your Clusterctl kind accordingly in your manifests and this error will be fixed16:23
airship-irc-bot<amir.boroufar> thanks16:25
airship-irc-bot<raliev> the actual version of cert-manager that is going to be installed by clusterctl is printed in logs: https://github.com/kubernetes-sigs/cluster-api/blob/25006fca1daa5c670ace6cde3b3a0a2d48bf03ce/cmd/clusterctl/client/cluster/cert_manager.go#L172 so you can always control and see what version is currently used and installed  by default, if not specified, it's the latest version:17:52
airship-irc-bothttps://github.com/kubernetes-sigs/cluster-api/blob/25006fca1daa5c670ace6cde3b3a0a2d48bf03ce/cmd/clusterctl/client/config/cert_manager.go#L22 which is currently 1.3.2: https://github.com/jetstack/cert-manager/releases/tag/v1.3.2  you can specify a tag with needed cert-manager image version here: https://github.com/airshipit/airshipctl/blob/master/manifests/function/clusterctl/clusterctl.yaml#L30 adding `tag` field17:52
airship-irc-bot<ratnopam.chakrabarti> Hi Core Team, please review https://review.opendev.org/c/airship/airshipctl/+/795319. This fixes CAPD zuul failure and addresses CAPD deployment using phase plan. Thanks in advance.19:35
airship-irc-bot<sidney.shiba> I used `cert-manager v1.3.2` and same issue, meaning worker nodes do not get created. Also noted that during the clusterctl-move the control plane `Machine` status stays in `Provisionned` instead of `Running` state. That hints me that some RBAC roles and/or binding are different between `cert-manager` deployed during `clusterctl-init-target` and during `initinfra-target` (capz cni).  Is there a way to retrieve the full22:23
airship-irc-bot`cert-manager` manifest used by `clusterctl-init-target` so I can compared?22:23

Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!