-
Notifications
You must be signed in to change notification settings - Fork 256
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
🌱 Build node images with cloud build #1746
base: main
Are you sure you want to change the base?
Conversation
✅ Deploy Preview for kubernetes-sigs-cluster-api-openstack ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: lentzi90 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 |
@lentzi90 it has to be tested with a Google Cloud account: you need to enable cloudbuild and to add the repo / branch where the |
Yeah I can see the cloud console, I can see the existing builds, but they are not triggered from "triggers" in cloud build and it seems I don't have privileges to add any. My guess is that it is all managed externally somehow. Perhaps they are triggered from test-infra? |
Co-authored-by: Mathieu Tortuyaux <[email protected]> Co-authored-by: Matthew Booth <[email protected]> Signed-off-by: Lennart Jern <[email protected]>
6927094
to
77c10e9
Compare
9b9c117
to
08e7227
Compare
2ee34f2
to
21a7a2f
Compare
39d7ca8
to
d813e41
Compare
Any clue why
(note the |
@lentzi90 very strange. It seems to come from the
|
d813e41
to
bc6558b
Compare
osimages/Makefile
Outdated
docker run --rm $(privileged) \ | ||
--network=host \ | ||
-v "$(OSIMAGE_DIR):/output" \ | ||
-e PACKER_LOG=1 \ |
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.
NOTE: Now it seems to work, we can remove this line that generates tones of logs.
From what I can see, it managed to build both flatcar images, but then it timed out for ubuntu. |
@lentzi90 commands over VNC... We already faced this: https://kubernetes.slack.com/archives/CFKJB65G9/p1679317697144409?thread_ts=1679302801.869119&cid=CFKJB65G9 |
Where/how would I change this? |
osimages/Makefile
Outdated
--network=host \ | ||
-v "$(OSIMAGE_DIR):/output" \ | ||
-e PACKER_FLAGS=" \ | ||
--var 'boot_wait=300s' \ |
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.
@lentzi90 #1746 (comment) you can change the value here.
f3b25f6
to
979fc28
Compare
The Kubernetes project currently lacks enough contributors to adequately respond to all PRs. This bot triages PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
I guess we do. My last attempt was to use GitHub actions. It looked promising at first, but kept failing from running out of disk space 🙁 |
Incidentally, I think I saw one of the infra folks mention that they didn't want anybody publishing container images from the staging repo because we get charged egress for it (but registry.k8s is ok). I'm guessing publishing OS images from our staging bucket would be even worse. The way we use them in our CI is presumably fine because they never leave GCP, but I suspect we should not routinely direct users to them for fear of blowing the credit card. @dims Do I have that right? |
The Kubernetes project currently lacks enough active contributors to adequately respond to all PRs. This bot triages PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle rotten |
/remove-lifecycle rotten |
The Kubernetes project currently lacks enough contributors to adequately respond to all PRs. This bot triages PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
/remove-lifecycle stale |
What this PR does / why we need it:
Add cloud build configuration for building node images.
Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close the issue(s) when PR gets merged):Fixes #1502
Special notes for your reviewer:
TODOs:
/hold