-
Notifications
You must be signed in to change notification settings - Fork 38
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
Clone GitHub repos to the local Gitea during install #212
base: main
Are you sure you want to change the base?
Conversation
…ernet traffic originating in the clusters later.
Hi @kispaljr. Thanks for your PR. I'm waiting for a nephio-project 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. |
…ned since my original solution
/assign @electrocucaracha @electrocucaracha, I see that you also made changes on how we handle stock git repos. Could you have a look if this was in line with your thinking? |
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.
I'm not able to test it, but I made few suggestions on it. Don't forget to include the license headers on the files
I put some comments on the draft. I think that makes sense, my only concern now it that prow hasn't triggered the CI yet. |
I think somebody (maybe @radoslawc ?) has to add an ok-to-test label to enable the CI tests |
/ok-to-test |
[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.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/retest |
Can someone help me with the install-integration and provision-linter tests? Is it an error in my code or in the tests? |
/kind cleanup |
- name: "Fetch kpt package: {{ item }}" | ||
ansible.builtin.command: | ||
cmd: "kpt pkg get --for-deployment --context {{ k8s.context }} '{{ nephio_example_repo_uri }}/{{ item }}@{{ nephio_pkg_version }}'" | ||
chdir: "/tmp" | ||
changed_when: false | ||
|
||
- name: "Render kpt package: {{ item }}" | ||
ansible.builtin.command: | ||
cmd: "kpt fn render --context {{ k8s.context }}" | ||
chdir: "/tmp/{{ item }}" | ||
changed_when: false | ||
|
||
- name: "Init kpt package: {{ item }}" | ||
ansible.builtin.command: | ||
cmd: "kpt live init --namespace default --context {{ k8s.context }}" | ||
chdir: "/tmp/{{ item }}" | ||
changed_when: false | ||
|
||
- name: "Apply kpt package: {{ item }}" | ||
ansible.builtin.command: | ||
cmd: "kpt live apply --namespace default --reconcile-timeout 3600 --context {{ k8s.context }}" | ||
chdir: "/tmp/{{ item }}" | ||
changed_when: false |
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.
/retest |
/retest |
@electrocucaracha could you take a look?
|
/retest |
…io-system namespace
/retest |
…prepare playbook to converge playbook
/retest |
I've submitted a PR in your fork to apply most of the suggestions. It's hard to review given that your fork requires rebase some commits, but if you want to take a look these are the changes |
@electrocucaracha
|
@kispaljr I'm still seeing some differences between these changes and this other |
0d5f139
to
0123635
Compare
/test install-integration |
``> @kispaljr I'm still seeing some differences between these changes and this other @electrocucaracha , you are right, they were different. So, I made the tip of my PR (0123635) identical to the tip of your PR (5a5c342). Here is the status of the nephio-webui ReplicaSet in the install-integration test logs for reference:
|
I tried to replicate it locally, but it worked. I'll give a second try to see if something changes. Regarding the e2e, it seems like it had issues to bring the Tunnel bridge up /retest |
@kispaljr: The following tests failed, say
Full PR test history. Your PR dashboard. 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. I understand the commands that are listed here. |
There is a way to run integration tests locally and review the state of the VM, you can use the following instruction |
What type of PR is this?
/kind cleanup
What this PR does / why we need it:
It clones GitHub repositories that are registered in porch to the local Gitea during install.
This is needed to make the sandbox more self-contained and it is also a first step toward making it work behind a corporate http proxy (because it avoids Internet traffic originating in the clusters).
Which issue(s) this PR fixes:
It is a step toward fixing nephio-project/nephio#409 , but it will not completely fix the issue.
** Notes to reviewer:
Git cloning is deliberately done directly on the host machine instead of a pod running in a management cluster. This way we only need to assume that the localhost can reach the Internet (i.e. http proxy vars are setup correctly), but we don't have to assume that workloads running in the clusters can also reach the internet (that would require the errorprone setting of the no_proxy variable, that is almost impossible to do correctly.)
Does this PR introduce a user-facing change?:
no.