[WIP] Initial PR for consuming gvproxy/macadam/cloud-init for crc-ng - #5025
[WIP] Initial PR for consuming gvproxy/macadam/cloud-init for crc-ng#5025praveenkumar wants to merge 28 commits into
Conversation
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
49de216 to
2cf49bb
Compare
|
/retest |
| return newCache(constants.GvproxyPath(), | ||
| url, | ||
| version, | ||
| func(executable string) (string, error) { |
There was a problem hiding this comment.
NewAdminHelperCache uses exactly the same function, might be desirable to share that code.
There was a problem hiding this comment.
Yes, we can share the code for getting the version info. May be a followup or new commit.
| } | ||
| // macadam version output format: "macadam version v0.2.0" | ||
| split := strings.Split(out, " ") | ||
| return strings.TrimSpace(split[len(split)-1]), nil |
There was a problem hiding this comment.
Same comment as for NewAdminHelperCache and NewGvproxyCache
| return errors.New("macadam executable is not cached") | ||
| } | ||
| if err := macadam.CheckVersion(); err != nil { | ||
| return errors.Wrap(err, "unexpected version of the macadam executable") |
There was a problem hiding this comment.
Let’s not add new uses of errors.Wrap in new code.
https://github.com/pkg/errors
This repository was archived by the owner on Dec 1, 2021. It is now read-only.
| {Name: "api-int", IP: "192.168.127.2"}, | ||
| {Name: "crc", IP: "192.168.126.11"}, | ||
| Records: []types.Record{ | ||
| {Name: "host", IP: net.ParseIP("192.168.127.254"), Regexp: nil}, |
There was a problem hiding this comment.
Is it required to set Regexp: nil?
| {Name: "api-int", IP: net.ParseIP("192.168.127.2"), Regexp: nil}, | ||
| {Name: "crc", IP: net.ParseIP("192.168.126.11"), Regexp: nil}, | ||
| }, | ||
| DefaultIP: net.ParseIP("192.168.127.2"), |
There was a problem hiding this comment.
DefaultIP was not there before.
| } | ||
| if err := cluster.EnsureGeneratedClientCAPresentInTheCluster(ctx, ocConfig, sshRunner, selfSignedCACert, adminClientCA); err != nil { | ||
| return errors.Wrap(err, "Failed to update user CA to cluster") | ||
| if err := sshRunner.CopyFileFromVM("/opt/kubeconfig", kubeconfigFilePath, 0644); err != nil { |
861432b to
7b070ed
Compare
|
|
||
| const userDataTemplate = `#cloud-config | ||
| runcmd: | ||
| - systemctl enable --now kubelet |
There was a problem hiding this comment.
@cfergeau why? this is required because our bundle have kubelet service disabled by default.
| content: '%s' | ||
| owner: core | ||
| permissions: '0600' | ||
| - path: /opt/crc/id_rsa.pub |
There was a problem hiding this comment.
no, /opt/crc/id_rsa.pub is the file which is required by mco ssh service https://github.com/crc-org/snc/blob/release-4.20/systemd/ocp-mco-sshkey.service here.
| - path: /opt/crc/pass_developer | ||
| content: '%s' | ||
| permissions: '0644' | ||
| - path: /opt/crc/ocp-custom-domain.service.done |
There was a problem hiding this comment.
Otherwise https://github.com/crc-org/snc/blob/release-4.20/systemd/ocp-custom-domain.service will fails and since it is Restart=on-failure so it is going to continue fail :( so better to have it as this magic file.
|
|
||
| // ExecMainExitTimestamp returns the exit timestamp of a service's main process. | ||
| // Returns empty string if the service has never run, otherwise returns the exit timestamp. | ||
| func (c Commander) ExecMainExitTimestamp(name string) (string, error) { |
There was a problem hiding this comment.
It return value is something which can be parsed as time but our aim is if there is timestamp which means the service is ready run and exited
$ systemctl show --property "ExecMainExitTimestamp" --value systemd-binfmt.service
Wed 2026-01-21 11:02:24 IST
9c795f3 to
e18270d
Compare
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
Made-with: Cursor
Co-authored-by: Cursor <cursoragent@cursor.com> Made-with: Cursor
This will help to use gvproxy as filename instead gvproxy-linux-amd64
Fix a misleading error and make sure parent directory exist before generating new keypair otherwise error occur when try to write the keypair on a non exist path.
Since with self sufficient bundle and cloud-init metadata pull secret should be applied automatic so just verify it instead apply. If it is not there that means something wrong with pull secret service in the bundle.
This commit have following - macadam helper to provide value based on macadam command run - cloud init helper to create user metadata - remove of libmachine api - updating vsock to work with gvproxy socket - Some todo which need to be improved
This will help to check if the service if run and finished successfully or not before checking the details in the cluster. Co-authored-by: Cursor <cursoragent@cursor.com>
With self sufficient bundle all the ca changes happen as part of service run in the VM so once that service finish successfully it is easy to just copy that kubeconfig file from VM to host. Co-authored-by: Cursor <cursoragent@cursor.com>
Made-with: Cursor
Introduce a new file containing the cursor commit rules for the project. This document outlines the guidelines for generating git commit messages, including the format, allowed commit types, and footer conventions. This addition aims to standardize commit practices across the codebase. Co-authored-by: Cursor <cursoragent@cursor.com>
Change the method of sourcing Go files in the Makefile to use the
`find` command, excluding the vendor directories. Without this if
we want to compile an uncommit source (mostly deleting a go file)
the git ls-files still have that file reference and build fails very early.
```
$ git status
On branch crc-ng
Changes not staged for commit:
(use "git add/rm <file>..." to update what will be committed)
(use "git restore <file>..." to discard changes in working directory)
modified: cmd/crc-embedder/cmd/embed.go
deleted: pkg/crc/machine/libvirt/constants.go
deleted: pkg/crc/machine/libvirt/driver_linux.go
deleted: pkg/crc/machine/libvirt/templates_linux.go
modified: pkg/crc/preflight/preflight_checks_linux.go
modified: pkg/crc/preflight/preflight_linux.go
modified: pkg/crc/preflight/preflight_linux_test.go
no changes added to commit (use "git add" and/or "git commit -a")
✔ ~/work/github/crc [crc-ng L|● 3✚ 4⚑ 17]
12:31 $ make cross
make: *** No rule to make target 'pkg/crc/machine/libvirt/constants.go', needed by 'out/macos-arm64/crc'. Stop.
```
Eliminate the libvirt package and its related files from the codebase, shifting the focus to qemu-kvm for virtualization checks as per macadam requirement. Update preflight checks to reflect this change, ensuring that the system verifies the presence of qemu-kvm instead of libvirt components. This refactor simplifies the code and aligns with the current macadam strategy. Co-authored-by: Cursor <cursoragent@cursor.com>
…d services Implement the WasSkippedDueToConditions method in the systemd Commander to check if service conditions are met. Update the WaitForServiceSuccessfullyFinished function to handle cases where services are skipped due to unmet conditions, indicating that their work was already completed in a previous run. This enhancement improves service management and logging clarity.
Since now macadam is used which by default using gvproxy so better to remove the virtual network implementation from the codebase.
Looks like our bundle now have service which automatic run growpart as part of cloud-init but then xfs_growfs is still required to grow xfs filesystem so we shouldn't return just after growpart and run xfs_growfs.
Update the removeCrcVM function to utilize macadam for VM status checks and removal. This change eliminates the previous libvirt dependency, streamlining the VM management process and improving error handling when removing the 'crc' VM.
As of now route-controller not able to expose the nodeport to host. We need to find a way for gvproxy side or route-conroller side to enable it.
It was initially added as part of ed9342 but since now we are moving to consume gvproxy and there is no virtual network running as part of crc daemon so this is no more required.
Since macadam right now not support resource resize as part of start => stop => resize resource => start so the test case is failing - crc-org/macadam#291
Since now openshift related changes shifted as part of the bundle which pass using cloud init file so changes to openshift side not going to work as part of stop => start. Test about developer user password change is moved to openshift feature where fresh crc instance is created.
Update EnsureVMPartitionSizeCorrect to use lsblk --bytes flag and parse sizes as byte values instead of relying on formatted strings with "G" suffix which fails because crc-ng create a disk for cloud init with size of 43K and parsing fails. This makes the parsing more reliable and consistent. Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
It was added before since there was no vsock support for 9p in windows, but since it is added so better to remove tcp fallback.
Generate and persist a hosts API token when the daemon starts and during preflight setup. Require the token as an `Authorization: Bearer` header on the `/hosts/add` and `/hosts/remove` admin-helper endpoints. Sync the same token into an OpenShift Secret so routes-controller can authenticate when updating the hosts file. Add unit tests for token creation and authorization checks.
|
@praveenkumar: The following tests failed, say
Full PR test history. Your PR dashboard. DetailsInstructions 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-sigs/prow repository. I understand the commands that are listed here. |
No description provided.