Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Creating clusters in non-default namespace using clusterctl fails at the pivot #735

Closed
sflxn opened this issue Feb 7, 2019 · 0 comments
Closed

Creating clusters in non-default namespace using clusterctl fails at the pivot #735

sflxn opened this issue Feb 7, 2019 · 0 comments
Labels
kind/bug Categorizes issue or PR as related to a bug.

Comments

@sflxn
Copy link

sflxn commented Feb 7, 2019

/kind bug

What steps did you take and what happened:

  1. Create machines.yaml and cluster.yaml. Add a namespace attribute and give it a new scope. Use clusterctl in a self-service workflow (using bootstrap and pivot).

What did you expect to happen:
New cluster would get created on the target cloud infrastructure and have machines and cluster objects created on the target cluster and scoped to the new namespace.

Anything else you would like to add:
Last two lines of the run,

I0205 16:36:38.368342   87810 kind.go:55] Ran: kind [delete cluster --name=clusterapi] Output:
F0205 16:36:38.368386   87810 create_cluster.go:59] unable to apply cluster api stack to target cluster: unable to pivot cluster API objects: error moving Cluster "test1": error creating cluster in namespace test: namespaces "test" not found

Environment:
vSphere but should also fail in other providers, based on the code in clusterdeployer.go.

  • Cluster-api version:
  • Kubernetes version: (use kubectl version): 1.11.3
  • OS (e.g. from /etc/os-release):
@k8s-ci-robot k8s-ci-robot added the kind/bug Categorizes issue or PR as related to a bug. label Feb 7, 2019
sflxn pushed a commit to sflxn/cluster-api that referenced this issue Feb 7, 2019
Fixed creating clusters in different namespaces when pivoting
66f7554 
There was a bug that prevented pivoting because a desired namespace was specified
in the cluster.yaml file.  It needs to ensure the the namespace on the target
cluster before pivoting.

Fixes kubernetes-sigs#735
sflxn pushed a commit to sflxn/cluster-api that referenced this issue Feb 7, 2019
Fixed creating clusters in different namespaces when pivoting
db673d8 
There was a bug that prevented pivoting because a desired namespace was specified
in the cluster.yaml file.  It needs to ensure the the namespace on the target
cluster before pivoting.  Also, ensuring namespace after getting the target cluster
kubeconfig requires a loop with exp backoff in some environments.

Fixes kubernetes-sigs#735
@sflxn sflxn mentioned this issue Feb 7, 2019
Merged
sflxn pushed a commit to sflxn/cluster-api that referenced this issue Feb 8, 2019
Fixed creating clusters in different namespaces when pivoting
0ead594 
There was a bug that prevented pivoting because a desired namespace was specified
in the cluster.yaml file.  It needs to ensure the the namespace on the target
cluster before pivoting.  Also, ensuring namespace after getting the target cluster
kubeconfig requires a loop with exp backoff in some environments.

Fixes kubernetes-sigs#735
sflxn pushed a commit to sflxn/cluster-api that referenced this issue Feb 8, 2019
Fixed creating clusters in different namespaces when pivoting
02260e1 
There was a bug that prevented pivoting because a desired namespace was specified
in the cluster.yaml file.  It needs to ensure the the namespace on the target
cluster before pivoting.  Also, ensuring namespace after getting the target cluster
kubeconfig requires a loop with exp backoff in some environments.

Fixes kubernetes-sigs#735
k8s-ci-robot pushed a commit that referenced this issue Feb 8, 2019
@k8s-ci-robot
Fixed creating clusters in different namespaces when pivoting (#736)
ae564ac 
There was a bug that prevented pivoting because a desired namespace was specified
in the cluster.yaml file.  It needs to ensure the the namespace on the target
cluster before pivoting.  Also, ensuring namespace after getting the target cluster
kubeconfig requires a loop with exp backoff in some environments.

Fixes #735
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/bug Categorizes issue or PR as related to a bug.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@sflxn @k8s-ci-robot