-
Notifications
You must be signed in to change notification settings - Fork 4.7k
Description
/kind bug
1. What kops
version are you running? The command kops version
, will display
this information.
Client version: 1.33.1 (git-v1.33.1)
2. What Kubernetes version are you running? kubectl version
will print the
version if a cluster is running or provide the Kubernetes version specified as
a kops
flag.
3. What cloud provider are you using?
GCE
4. What commands did you run? What is the simplest way to reproduce this issue?
kops create cluster cluster.k8s.local
--topology private
--api-loadbalancer-type internal
--networking cilium-etcd
--bastion
5. What happened after the commands executed?
Cluster built, but cilium pod continually restarted as they couldn't reach APISERVER:4003. Confirmed that APISERVER isn't configured to listen on port 4003.
6. What did you expect to happen?
7. Please provide your cluster manifest. Execute
kops get --name my.example.com -o yaml
to display your cluster manifest.
You may want to remove your cluster name and other sensitive information.
8. Please run the commands with most verbose logging by adding the -v 10
flag.
Paste the logs into this report, or in a gist and provide the gist link here.
9. Anything else do we need to know?