zap51 opened a new issue, #8718:
URL: https://github.com/apache/cloudstack/issues/8718

   <!--
   Verify first that your issue/request is not already reported on GitHub.
   Also test if the latest release and main branch are affected too.
   Always add information AFTER of these HTML comments, but no need to delete 
the comments.
   -->
   
   ##### ISSUE TYPE
   <!-- Pick one below and delete the rest -->
    * Bug Report
   
   ##### COMPONENT NAME
   <!--
   Categorize the issue, e.g. API, VR, VPN, UI, etc.
   -->
   ~~~
   CKS
   ~~~
   
   ##### CLOUDSTACK VERSION
   <!--
   New line separated list of affected versions, commit ID for issues on main 
branch.
   -->
   
   ~~~
   4.16.1.0 onwards
   ~~~
   
   ##### CONFIGURATION
   <!--
   Information about the configuration if relevant, e.g. basic network, 
advanced networking, etc.  N/A otherwise
   -->
   ~~~
   Advanced Networking
   ~~~
   
   ##### OS / ENVIRONMENT
   <!--
   Information about the environment if relevant, N/A otherwise
   -->
   ~~~
   Ubuntu 20.04 and later
   ~~~
   
   ##### SUMMARY
   <!-- Explain the problem/feature briefly -->
   A Kubernetes Cluster managed by CKS fails to acquire external IP for the 
service of type "LoadBalancer" when the cluster / node names have upper case 
letters.
   
   ##### STEPS TO REPRODUCE
   <!--
   For bugs, show exactly how to reproduce the problem, using a minimal 
test-case. Use Screenshots if accurate.
   
   For new features, show how the feature would be used.
   -->
   
   <!-- Paste example playbooks or commands between quotes below -->
   ~~~
   1. Create a cluster with some name which contains upper case characters like 
for example "Kubernetescl34t"
   2. Nodes come online with lower case letters
   # kubectl get no
   NAME                                  STATUS   ROLES           AGE   VERSION
   kubernetescl34t-control-18dee810e29   Ready    control-plane   88s   v1.28.4
   kubernetescl34t-control-18dee813b32   Ready    control-plane   75s   v1.28.4
   kubernetescl34t-control-18dee81618f   Ready    control-plane   74s   v1.28.4
   kubernetescl34t-node-18dee818726      Ready    <none>          76s   v1.28.4
   3. Run a sample pod and create a service of type "LoadBalancer"
   # kubectl run --image=nginx nginx
   pod/nginx created
   root@Kubernetescl34t-control-18dee810e29:~# kubectl expose pod/nginx 
--type=LoadBalancer --port=80
   service/nginx exposed
   4. The external IP doesn't get acquired and the service-controller reports 
the below
   # kubectl describe svc/nginx
   Name:                     nginx
   Namespace:                default
   Labels:                   run=nginx
   Annotations:              <none>
   Selector:                 run=nginx
   Type:                     LoadBalancer
   IP Family Policy:         SingleStack
   IP Families:              IPv4
   IP:                       10.96.80.24
   IPs:                      10.96.80.24
   Port:                     <unset>  80/TCP
   TargetPort:               80/TCP
   NodePort:                 <unset>  31692/TCP
   Endpoints:                10.44.0.4:80
   Session Affinity:         None
   External Traffic Policy:  Cluster
   Events:
     Type     Reason                  Age               From                
Message
     ----     ------                  ----              ----                
-------
     Normal   EnsuringLoadBalancer    6s (x4 over 43s)  service-controller  
Ensuring load balancer
     Warning  SyncLoadBalancerFailed  6s (x4 over 42s)  service-controller  
Error syncing load balancer: failed to ensure load balancer: could not find 
network
   ~~~
   
   Mailing list reference: 
https://lists.apache.org/thread/bm1g6lmx6pv2tg8v331rtjn0ytxm4xpj
   
   <!-- You can also paste gist.github.com links for larger files -->
   
   ##### EXPECTED RESULTS
   <!-- What did you expect to happen when running the steps above? -->
   
   ~~~
   The external IP should be acquired. CKS should enforce only lowercase names 
for the cluster and the nodes.
   ~~~
   
   ##### ACTUAL RESULTS
   <!-- What actually happened? -->
   
   <!-- Paste verbatim command output between quotes below -->
   ~~~
   Events:
     Type     Reason                  Age               From                
Message
     ----     ------                  ----              ----                
-------
     Normal   EnsuringLoadBalancer    6s (x4 over 43s)  service-controller  
Ensuring load balancer
     Warning  SyncLoadBalancerFailed  6s (x4 over 42s)  service-controller  
Error syncing load balancer: failed to ensure load balancer: could not find 
network
   ~~~
   


-- 
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