support oci in helm-app and custom_cni

[borislitv]

What type of PR is this?
/kind feature

What this PR does / why we need it:
support oci helm repo in helm-app
support oci helm repo in custom_cni

Which issue(s) this PR fixes:
#10712

Special notes for your reviewer:
custom_cni example vars:

custom_cni_chart_release_name: "calico"
custom_cni_chart_namespace: "tigera-operator"
custom_cni_chart_ref: "oci://test.registry.net:5000/helm-charts/calico"
custom_cni_chart_version: "0.3.1"
custom_cni_chart_auth_username: "test-user"
custom_cni_chart_auth_password: "test-password"

Does this PR introduce a user-facing change?:

support oci helm repo

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: borislitv
Once this PR has been reviewed and has the lgtm label, please assign floryut for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[k8s-ci-robot]

Hi @borislitv. Thanks for your PR.

I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

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-sigs/prow repository.

[tico88612]

/ok-to-test

[borislitv]

/retest

[borislitv]

@tico88612 @yankay Hi guys, everything seems to work
Please see my changes for approval

[borislitv]

rebased @tico88612 @yankay FYI

[tico88612]

Why do you need to change the testcase script?
Can you explain the need for this behavior?

[borislitv]

Why do you need to change the testcase script?
Can you explain the need for this behavior?

Apparently the dependence is updated after pr merge, in any case now there is an old library and the test is falling. No image with new dependencies appears on the request pool. Probably after the merge can be removed.
/retest

[borislitv]

@tico88612 I read the documentation again, kubernetes.core collection is part of the ansible package, so it needs to be updated via ansible-galaxy. As a result, through the new image should work, but apparently will not work through the local environment (made through pip
). Therefore, I need advice: how to solve such problems with dependences?

[yankay]

The CI needs to pass

[borislitv]

The CI needs to pass

it doesn't seem to have crashed because of my changes, all the tests passed before the rebase, but I'll look again. And what to do with dependencies?
p.s. fixed with another rebase

[borislitv]

According to the changelog https://github.com/ansible-community/ansible-build-data/blob/main/11/CHANGELOG-v11.md#unchanged-collections the best way would be to upgrade ansible to 11.3.0
Is it possible to update ansible version? I could try

[tico88612]

@borislitv #11924 is WIP.

[borislitv]

@borislitv #11924 is WIP.

great news! Unfortunately I need at least 11.3.0, otherwise my pull request should wait for an update.

[k8s-ci-robot]

PR needs rebase.

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-sigs/prow repository.

[borislitv]

I'll wait #11924 and then try to up ansible version -> 11.3.0