-
Notifications
You must be signed in to change notification settings - Fork 41
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
chore: update gha in main #374
base: main
Are you sure you want to change the base?
Conversation
Failing with this error.
|
.github/workflows/main.yml
Outdated
@@ -109,6 +109,12 @@ jobs: | |||
run: | | |||
make docker-build | |||
make docker-push | |||
- name: Create K8s 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.
@gatici,
FYI, I think you can use this GHA: https://github.com/marketplace/actions/kind-cluster instead
Please check whether the issue with the CRDs (e2e GHA) is due to the registries I removed in this commit: gab-arrobo/aether-in-a-box@22a1595 |
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.
Shouldn't this use the shared workflow files? For testing, I think we can target the branch directly.
This PR is only for testing and never will be merged. |
@gatici @ghislainbourgeois, I think we can avoid using the DockerHub credentials by using a local registry with the help of this GitHub Action (https://docs.docker.com/build/ci/github-actions/local-registry/). What do you think? The only thing is that I am pretty certain current Helm Charts do not support different registry per NF's image. That is, all images should come from the same registry. However, this is something we can properly address in the Sdcore Hel Charts |
Hello @gab-arrobo , |
@gatici,
|
Hello Gabriel,
Here are the latest results.
|
Signed-off-by: gatici <[email protected]>
Signed-off-by: gatici <[email protected]>
Signed-off-by: gatici <[email protected]>
Signed-off-by: gatici <[email protected]>
Signed-off-by: gatici <[email protected]>
Signed-off-by: gatici <[email protected]>
Signed-off-by: gatici <[email protected]>
Signed-off-by: gatici <[email protected]>
Signed-off-by: gatici <[email protected]>
Signed-off-by: gatici <[email protected]>
Signed-off-by: gatici <[email protected]>
Signed-off-by: gatici <[email protected]>
Signed-off-by: gatici <[email protected]>
Signed-off-by: gatici <[email protected]>
Signed-off-by: gatici <[email protected]>
Signed-off-by: gatici <[email protected]>
Signed-off-by: gatici <[email protected]>
Signed-off-by: gatici <[email protected]>
Signed-off-by: gatici <[email protected]>
Signed-off-by: gatici <[email protected]>
Signed-off-by: gatici <[email protected]>
Signed-off-by: gatici <[email protected]>
Signed-off-by: gatici <[email protected]>
Signed-off-by: gatici <[email protected]>
Signed-off-by: gatici <[email protected]>
Signed-off-by: gatici <[email protected]>
Signed-off-by: gatici <[email protected]>
Signed-off-by: gatici <[email protected]>
Signed-off-by: gatici <[email protected]>
Signed-off-by: gatici <[email protected]>
Signed-off-by: gatici <[email protected]>
Signed-off-by: gatici <[email protected]>
Signed-off-by: gatici <[email protected]>
1b3676d
to
630167e
Compare
Signed-off-by: gatici <[email protected]>
# Copyright 2023 Canonical Ltd. | ||
# Copyright 2024 Canonical Ltd. |
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.
Why do you change this? You can leave it as 2023-present
@@ -63,16 +42,15 @@ jobs: | |||
args: -v --config ./.golangci.yml | |||
|
|||
hadolint: | |||
name: hadolint | |||
name: Dockerfile linter |
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 would delete the name
name: Dockerfile linter |
sudo microk8s addons repo add community https://github.com/canonical/microk8s-community-addons --reference feat/strict-fix-multus | ||
sudo microk8s enable multus | ||
sudo microk8s kubectl -n kube-system rollout status daemonset/kube-multus-ds | ||
sudo microk8s kubectl auth can-i create network-attachment-definitions |
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.
As far I know and tested, you do not need sudo
in GitHub runners
sudo microk8s addons repo add community https://github.com/canonical/microk8s-community-addons --reference feat/strict-fix-multus | |
sudo microk8s enable multus | |
sudo microk8s kubectl -n kube-system rollout status daemonset/kube-multus-ds | |
sudo microk8s kubectl auth can-i create network-attachment-definitions | |
microk8s addons repo add community https://github.com/canonical/microk8s-community-addons --reference feat/strict-fix-multus | |
microk8s enable multus | |
microk8s kubectl -n kube-system rollout status daemonset/kube-multus-ds | |
microk8s kubectl auth can-i create network-attachment-definitions |
|
||
- name: Export kubeconfig file | ||
run: | | ||
sudo microk8s kubectl config view --raw > $HOME/.kube/config |
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.
Same as previous comment
sudo microk8s kubectl config view --raw > $HOME/.kube/config | |
microk8s kubectl config view --raw > $HOME/.kube/config |
cd $(HOME) && \ | ||
git clone https://github.com/gab-arrobo/aether-in-a-box && \ | ||
cd aether-in-a-box && \ | ||
yq -i '.5g-control-plane.images |= {"amf": "localhost:32000/5gc-amf:amf-testing"}' sd-core-5g-values.yaml && \ |
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.
yq -i '.5g-control-plane.images |= {"amf": "localhost:32000/5gc-amf:amf-testing"}' sd-core-5g-values.yaml && \ | |
yq -i '.5g-control-plane.images.tags |= {"amf": "localhost:32000/5gc-amf:amf-testing"}' sd-core-5g-values.yaml && \ |
main
branch.main
branch or to any tags that match the patternv
.unit-tests
,lint
, andstaticcheck
jobs passes, runs E2E tests.Important: We used a dummy docker repository here because a pull request can not access project secrets before merge.
Now, docker token is exposed which shouldn't. We need to find to a way to handle it in better way.
VERSION
file, new releases are tagged.docker.io
).VERSION
file.