MejdiB opened a new issue #6128:
URL: https://github.com/apache/cloudstack/issues/6128


   ##### ISSUE TYPE
    * Bug Report
    * Improvement
   
   ##### COMPONENT NAME
   ~~~
   API
   ~~~
   
   ##### CLOUDSTACK VERSION
   ~~~
   4.16.1
   ~~~
   
   ##### CONFIGURATION
   Cloudstack 4.16.1 Environment Advanced Zone with Security Groups. There is a 
shared default Network with a pool of IP addresses available for instances.
   
   ##### OS / ENVIRONMENT
   RHEL 8.4 is used for cloudstack management servers and hosts.
   
   ##### SUMMARY
   In ACS v4.15.x, we used CoreOS template for our KCS and it worked in our 
environment. The node instances were setup with the default Security Group of 
the account and the nodes were accessible from the Management Servers. With 
Cloudstack 4.16.0 and above, Kubernetes Cluster are set up with the new System 
VM template based on Debian. Setting up a Kubernetes Cluster with the new 
System VM template fails, because the Management Server have no access to the 
control node, but to others. I assume this is due to the missing Security Group 
property for the instance. 
   
   ##### STEPS TO REPRODUCE
   ~~~
   - ACS Environment Advanced Zone (maybe also Basic Zone) with Security Group 
option
   - Enable Kubernetes Service for the Zone
   - Default Shared Network with a set of IP addresses
   - Create a Kubernetes Cluster with 1.20 or above (in my case 1.23.3) would 
run into an error due to inability of the Management Server to access the 
control node 
   ~~~
   
   ##### EXPECTED RESULTS
   ~~~
   - A working Kubernetes Cluster v1.23.3 (or lower)
   - Manually adding or removing a Security Group to an instance would help me 
out, but I have found no feature on the UI..
   ~~~
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to