marko_uskokovic's Posts

I have tried CSE.next on multisite setup, where I have two VCD sites paired on system and organization level. So, sites are rs-bg-1-ec and rs-bg-2-ec and I can see VDCs and VMs from both sites in VCD. Also, in CSE UI plugin on rs-bg-2-ec site I can see k8s clusters from both sites: If I click on cse4-rs-bg-1-test-1 link, it will open rs-bg-1-ec site in new browser tab, but it will not accept my current SSO login and I will need to login again to manage my cluster. Annoyance, but bearable. The real problem is, if I login to rs-bg-2-ec site, and go to another site by SSO, and then open CSE UI plugin, it will not be able to show any clusters, it will display message "Error: Failed to fetch Kubernetes clusters" There is 401 Unauthorized HTTP request to rs-bg-1-ec site's /api/session url and there is a "CSE UI: Error fetching sites" message in browser console.   Note: Similar problems were noticed in CSE 3.1 when using multisite setup.    

I accidentally deleted load balancer rule for 6443 port, and was hoping that CSE will re-create it because it is needed for cluster to work correctly, but that does not happen. Is that load balancer supposed to be managed by CSE and re-created or modified as needed?

Sometimes it happens that node count is not correct even after cluster progresses to Ready state - different values are shown in CSE plugin than it is visible in kubectl command and it stays like that even afer 48h  

After provisioning of CSE.next cluster, I got storage class created: kubectl --kubeconfig cse4-2 get storageclasses.storage.k8s.io NAME PROVISIONER RECLAIMPOLICY VOLUMEBINDINGMODE ALLOWVOLUMEEXPANSION AGE default-storage-class-1 (default) named-disk.csi.cloud-director.vmware.com Delete Immediate false 5h1m   But it is not visible in CSE plugin, it just shows N/A    

I have tried to access control plane and worker nodes after provisioning (but I am unable to login because SSH public key I entered during provisioning is not configured on nodes which I described in another thread) so my host SSH key is recorded in my client for future use. But after rebooting the node, host SSH key is changed: [me@home ~]$ ssh -p 22 root@172.16.172.16 root@172.16.172.16's password: Permission denied, please try again. root@172.16.172.16's password: reboot happens here [me@home ~]$ ssh -p 22 root@172.16.172.16 @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ @ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @ @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY! Someone could be eavesdropping on you right now (man-in-the-middle attack)! It is also possible that a host key has just been changed.   Is that supposed to happen or is it because cloud-init is failing to configure nodes? I don't think it is a good thing to change host SSH key every time node is restarted... 

After successful cluster provisioning (State: Ready) I can not login to any node using SSH public key I provided during setup of cluster. Also, I am not able to login to nodes using password that VCD autogenerated in "Guest OS Customization" (nor with manually specified password). Since I can not login to nodes I can't see logs of cluster provisioning. Only thing I can see are cloud-init errors after boot:   control-plane control-plane-after-reboot worker worker-after-reboot 

This is my first try to provision cse.next k8s cluster, and it fails while creating EPHEMERAL_TEMP_VM with ScriptInitError and later with EphemeralVMError, and It doesn't even start.   VMware Cloud Director version: 10.3.2.19473806   I have attached whole cse log from journalctl -lu cse