-
Notifications
You must be signed in to change notification settings - Fork 29
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
adding a periodic job for testing on eks cluster #512
Conversation
Signed-off-by: RinkiyaKeDad <arshsharma461@gmail.com>
Hi @RinkiyaKeDad. Thanks for your PR. I'm waiting for a jetstack member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Signed-off-by: RinkiyaKeDad <arshsharma461@gmail.com>
Signed-off-by: RinkiyaKeDad <arshsharma461@gmail.com>
Signed-off-by: RinkiyaKeDad <arshsharma461@gmail.com>
Signed-off-by: RinkiyaKeDad <arshsharma461@gmail.com>
Signed-off-by: RinkiyaKeDad <arshsharma461@gmail.com>
/release-note-none |
Signed-off-by: Arsh Sharma <arshsharma461@gmail.com>
Signed-off-by: Arsh Sharma <arshsharma461@gmail.com>
Signed-off-by: Arsh Sharma <arshsharma461@gmail.com>
Signed-off-by: Arsh Sharma <arshsharma461@gmail.com>
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.
Have a couple of doubts :)
# extra_refs: | ||
# - org: jetstack | ||
# repo: cert-manager | ||
# base_ref: master |
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.
What do these do? Are they needed?
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.
It specifies what repository this Prow job clones when it runs.
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! Would you also know where it clones the repo? For example right now when we run the golang image we are in /go
at the start. So if we specify this, would we be inside /go/cert-manager
or would we still be in /go
but have the cert-manager
folder already cloned for us?
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.
From a quick check it's cloned at /home/prow/go/src/github.com/jetstack/cert-manager
and Prow sets that as workingDir
for the test container.
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.
By workingDir
do you mean that at the launch of the container we would be at /home/prow/go/src/github.com/jetstack/cert-manager
? If yes, then if we add another repo would the first one be the workingDir
?
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.
By workingDir do you mean that at the launch of the container we would be at /home/prow/go/src/github.com/jetstack/cert-manager?
Yep- it's the the workingDir in the container spec.
If yes, then if we add another repo would the first one be the workingDir
Looking at the code here looks like that would happen by default, but it seems like we can also set work_dir: true
for a particular ref to configure which one should become workingDir
.
I've not tried cloning more than one myself.
# labels: | ||
# preset-service-account: "true" | ||
# preset-dind-enabled: "true" | ||
# preset-bazel-remote-cache-enabled: "true" | ||
# preset-bazel-scratch-dir: "true" | ||
# preset-cloudflare-credentials: "true" | ||
# preset-venafi-tpp-credentials: "true" | ||
# preset-venafi-cloud-credentials: "true" |
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.
Which ones will we need?
# preset-venafi-cloud-credentials: "true" | ||
spec: | ||
containers: | ||
- image: eu.gcr.io/jetstack-build-infra-images/bazelbuild:20210323-ad5071a-3.7.2 |
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.
How do I specify the golang-aws
image that we built here?
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.
You will first need to add the infra to build that image so it gets pushed to Jetstack Build Infra images GCR and then you can get the image sha from there. So probably the commits that build the image need to go in a PR before the PR that adds this Prow job.
- name: AWS_ACCESS_KEY_ID | ||
value: "???" | ||
- name: AWS_SECRET_ACCESS_KEY | ||
value: "???" |
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.
We can't have the access keys on GitHub so how will this work?
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.
It'll probably need to be a Secret
in the cluster where the Prow job runs. The Prow job can then be configured to consume it via a preset like we do it with i.e Venafi creds- preset defined here and consumed added to the job here. (The actual Secret
would need to be created in the cluster separately).
Signed-off-by: Arsh Sharma <arshsharma461@gmail.com>
Signed-off-by: Arsh Sharma <arshsharma461@gmail.com>
Signed-off-by: Arsh Sharma <arshsharma461@gmail.com>
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.
/hold because of things mentioned in the review.
preset-aws-credentials: "true" | ||
spec: | ||
containers: | ||
- image: <to-be-replaced> |
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.
This.
cd.. && \ | ||
cd.. && \ | ||
cd cert-manager && \ | ||
./devel/run-e2e.sh --ginkgo.focus "Public ACME Server HTTP01 Issuer" --acme-server-url=https://acme-staging-v02.api.letsencrypt.org/directory --ingress-controller-domain=aws.e2e-tests.cert-manager.io --testing-acme-email=<need-to-replace-this> --kubernetes-config=../test-infra/aws/kubeconfig_cert-manager-cluster; |
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.
--testing-acme-email=<need-to-replace-this>
this.
Signed-off-by: Arsh Sharma <arshsharma461@gmail.com>
/unhold |
/ok-to-test |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: jakexks, RinkiyaKeDad The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
@RinkiyaKeDad: Updated the
In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Signed-off-by: RinkiyaKeDad arshsharma461@gmail.com
/assign @jakexks