-
Notifications
You must be signed in to change notification settings - Fork 40k
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.
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
Detect the project in which the federation of clusters are being created and point the federation docker registry to that project. #26951
Conversation
@madhusudancs great idea, lgtm. |
Yes, thanks! |
25056c0
to
0a79f5c
Compare
Rebased the PR to only contain the relevant commit. Added LGTM label. |
|
||
# Populates $PROJECT | ||
detect-project | ||
if [[ ${PROJECT} == *':'* ]] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Shouldnt this also check that FEDERATION_PUSH_REPO_BASE is empty? Otherwise, I will always get this error if my project has ":" in it (which I think is true for @quinton-hoole's project)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also optional: we dont need to run this whole code (including calling detect-project) if FEDERATION_PUSH_REPO_BASE is set already.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for catching that. Fixed.
Removing LGTM as per the comment above. |
…ntrol-todo Automatic merge from submit-queue Add a TODO to enable admission control in federation apiserver when the support is added. Only the last commit here needs review. Depends on #26951. cc @kubernetes/sig-cluster-federation [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/.github/PULL_REQUEST_TEMPLATE.md?pixel)]()
Automatic merge from submit-queue Updating e2e docs with instructions on running federation tests Last two commits are for review. Depends on #26951 \cc @madhusudancs @quinton-hoole @nikhiljindal [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/.github/PULL_REQUEST_TEMPLATE.md?pixel)]()
…ted and point the federation docker registry to that project.
0a79f5c
to
498168b
Compare
@nikhiljindal Fixed. PTAL. |
|
||
# If $FEDERATION_PUSH_REPO_BASE isn't set set the GCR registry name based on the | ||
# detected project name. | ||
if [[ -z "${FEDERATION_PUSH_REPO_BASE}" ]]; then |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
On second thought, should we also check that KUBERNETES_PROVIDER = gce or gke?
I assume this wont work on vagrant and aws?
We should also update the documentation that colin added to say that the repo env var is optional on gce and gke. |
Feel free to add the LGTM label once you have added the KUBERNETES_PROVIDER check |
e439ec2
to
c7a4401
Compare
Addressed the comments. Adding LGTM. |
@k8s-bot test this [submit-queue is verifying that this PR is safe to merge] |
GCE e2e build/test passed for commit c7a4401. |
Automatic merge from submit-queue |
Automatic merge from submit-queue Updating e2e docs with instructions on running federation tests Last two commits are for review. Depends on kubernetes#26951 \cc @madhusudancs @quinton-hoole @nikhiljindal [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/.github/PULL_REQUEST_TEMPLATE.md?pixel)]()
…ect-registry-base Automatic merge from submit-queue Detect the project in which the federation of clusters are being created and point the federation docker registry to that project. Only the last commit here needs review. Depends on kubernetes#26950. cc @colhom @kubernetes/sig-cluster-federation [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/.github/PULL_REQUEST_TEMPLATE.md?pixel)]()
Only the last commit here needs review.
Depends on #26950.
cc @colhom @kubernetes/sig-cluster-federation