Open xqzhang2015 opened 2 months ago
@xqzhang2015 Could you try using the latest kOps release?
@hakman Yes, I could. Here I'm just curious about how the mechanism/code works here(in 1.25), which maybe I don't know about it thoroughly.
@hakman Yes, I could. Here I'm just curious about how the mechanism/code works here(in 1.25), which maybe I don't know about it thoroughly.
Based on what I see in 1.25 code, should be part of the IG spec. In later kOps versions, it is implicit.
/kind bug
1. What
kops
version are you running? The commandkops version
, will display this information.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 akops
flag.3. What cloud provider are you using? AWS
4. What commands did you run? What is the simplest way to reproduce this issue?
kops create -f test.yaml
5. What happened after the commands executed?
6. What did you expect to happen?
https://github.com/kubernetes/kops/blob/dc41ea691ae6a1798d4ee4954b2dd327762fd588/upup/pkg/fi/cloudup/new_cluster.go#L980
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?