Release versions 3.3.0 and 5.1.0

[yurnov]

As Ansible 11 was released and included kubernetes.core collections 5.0.0 means that branch stable-5 become the default one for the most of users who install ansible comunity package as pip install ansible, and documentation from the branch stable-5 (more specifically, to the released versions 5.x.y from that branch) appeared in the ansible documentation site.

However, since Jun 10 when 5.0.0 was released, we have had a lot of smaller and bigger changes that are not included in any released version of the collection kubernetes.core, and some of them have even not been cherry-picked to the stable-5 branch, which led, for the example that ansible galaxy contains deprecated communication channels.

So, it's time to release a new release from the branch stable-5 (that should be 5.1.0) and, probably stable-3 (that should be 3.2.0 in this case) but it's less important.

SUMMARY

Release a new version 5.1.0

To do that, some PRs that weren't cherry-picked to stable-5 should be merged in that branch (label backport-5 to be added):

• Doc: update changelog with release 3.2.0 #750
• fix shields.io badges in README.md #749
• Fix waiting for daemonset when desired number of pods is 0 #756
• Bump the ansible-lint version to 24.7.0 #765 (optional, it can be skipped as it does not affect final build, however, it is nice to have for consistency between branches)
• Update Readme to match the template #767
• README: Add Communication section with Forum information #774
• CONTRIBUTING.md remove IRC #778
• Make k8s_drain work when only one pod is present #770
• Update README.md with removing outdated communication channels #790
• Remove kubevirt integration test workflow #806

The listed above PRs are merged to main but don't have the label backport-5 and are missed in branch stable-5.

UPDATE: to achieve working CI, the following is required:

• Fix helm tests #827 main branch
• Fix helm integration tests #830 main branch
• [PR #827/c8a33c71 backport][stable-5] Fix helm tests #828 (backport to stable-5 for Fix helm tests #827)
• [PR #830/7559b659 backport][stable-5] Fix helm integration tests #833 (backport to stable-5 for Fix helm integration tests #830)
• Backport to Stable-3: Fix helm tests (#827) and Fix helm integration tests (#830) #829 (backport to stable-3 for Fix helm tests #827)
• [PR #830/7559b659 backport][stable-3] Fix helm integration tests #832 or Backport to Stable-3: Fix helm tests (#827) and Fix helm integration tests (#830) #829 (backport to stable-3 for Fix helm integration tests #830)
• fix CI issue (linters), issue Failed linters in CI due to https://github.com/ansible/ansible-lint/issues/4477 #846, fix prepared as fix linters issue in CI caused by uplift of ansible-compat #848 and
• dropback fix linters issue in CI caused by uplift of ansible-compat #848 to stable-5 ([PR #848/159a63af backport][stable-5] fix linters issue in CI caused by uplift of ansible-compat #849)
• dropback fix linters issue in CI caused by uplift of ansible-compat #848 and stable-3 (Backport "fix linters in github actions (#848)" to stable-3 #850)
• fix unstable k8_drain in integration test (Clean up test namespace #852) + backport to stable-3 and stable-5

On top of that, the following PRs are to be merged into main:

• helm_registry_auth module to authenticate in OCI registry #800 + backport to stable-5
• Remove kubeconfig value from module invocation log #826 + backport to stable-5 + backport to stable-5
• helm_pull: Silence false no_log warning #796
• backport helm_pull: Silence false no_log warning #796 to stable-5 (and optionally to stable-3)
• trivial doc: replace 2.5.0 with 3.0.0 #831 with [skip-changelog] label
• [PR #831/bc0de24c backport][stable-5] trivial doc: replace 2.5.0 with 3.0.0 #856 backport trivial doc: replace 2.5.0 with 3.0.0 #831 to stable-5
• [PR #831/bc0de24c backport][stable-3] trivial doc: replace 2.5.0 with 3.0.0 #855 backport trivial doc: replace 2.5.0 with 3.0.0 #831 to stable-3
• Remove deprecated .github/stale.yml to address #837 #838 with [skip-changelog], no backport required (optional)

And finally:

• create PR into stable-3 with release 3.3.0, add a tag when merged;
• create PR into stable-5 with release 5.1.0, do not forget to add 3.3.0 into changelog, add tag when merged;
• create PR to main with port 5.1.0 update and change version in galaxy.yaml to 5.2.0-dev0 to easy see that it's not released version in the output of ansible-galaxy collection list when collection is installed from git.
• notify @newsbot:ansible.im to include released versions 3.3.0 and 5.1.0 in the next Ansible Bullhorn.

ISSUE TYPE

• Feature Idea

COMPONENT NAME

kubernetes.core

ADDITIONAL INFORMATION

I can create the above-mentioned PRs (in the "and finally" part) in the similar way as #746, but need support from maintainers with code review, merge and tags.

[yurnov]

Backport of #767 to stable-3 created as #822 due to merge conflict resolved manually

[yurnov]

backport of #774 to stable-5 created as #823 due to patchback bot fail

[yurnov]

I have updated issue to reflect the actual status and additional effort

[yurnov]

Updated with CI issue (linters), please find #848.

@abikouo, would you like to review that PR?

[yurnov]

PR #802 requires actions from @b0z02003, and he didn't respond to a request from @abikouo. I think that this can be skipped in release 5.1.0 (alternatively, I can help with the rebase and testing part, if the PR author will allow me to commit to b0z02003/kubernetes.core)

[gravesm]

I think we should skip it and do the release the beginning of next week.

[yurnov]

I think we should skip it and do the release the beginning of next week.

Sure. Thanks, @gravesm for your (and @abikouo) valuable support with this issue, I didn't expect this amount of CI-related work.

Would it be ok if I create PRs for the remaining part?

[gravesm]

Yeah, that would be great. Thanks for your help in pushing this forward.

[yurnov]

Yeah, that would be great. Thanks for your help in pushing this forward.

Thanks, I will do in Monday.

BTW, would you please add skip-changelog to #860 and #859 to merge them?

[gravesm]

BTW, would you please add skip-changelog to #860 and #859 to merge them?

They're both merged.

[yurnov]

BTW, would you please add skip-changelog to #860 and #859 to merge them?

They're both merged.

sorry, my fault, I meant #855 and #856 that is backports of #831, they are still opened with failed CI on changelog

[gravesm]

Ah, sorry, missed these.

[b0z02003]

PR #802 requires actions from @b0z02003, and he didn't respond to a request from @abikouo. I think that this can be skipped in release 5.1.0 (alternatively, I can help with the rebase and testing part, if the PR author will allow me to commit to b0z02003/kubernetes.core)

I'm so sorry for the late reply. I do understand if the PR skips the next release, in the mean time, I've just rebased it and added @yurnov as a contributor. I'll try to look for the failing integration test on my part today and, hopefully, I'll be able to provide you with a clean PR for this next release (still, I'll understand if you skip it).

[yurnov]

PR #802 requires actions from @b0z02003, and he didn't respond to a request from @abikouo. I think that this can be skipped in release 5.1.0 (alternatively, I can help with the rebase and testing part, if the PR author will allow me to commit to b0z02003/kubernetes.core)

I'm so sorry for the late reply. I do understand if the PR skips the next release, in the mean time, I've just rebased it and added @yurnov as a contributor. I'll try to look for the failing integration test on my part today and, hopefully, I'll be able to provide you with a clean PR for this next release (still, I'll understand if you skip it).

Let see how it will work in monday

[yurnov]

Hi @gravesm @abikouo,

during the weekend the CI part for #802 was completed, should we include this PR in the release? Could you please take a look?

Both options, to include this PR, or to release without and keep 802 and #786 for the next release will be fine for me.

[gravesm]

Let's continue with the release as planned and leave these for the next release. We can probably try and plan on a 5.2.0 release in a month.

[yurnov]

PR for 3.3.0 #863
PR for 5.1.0 #865

[yurnov]

Releases 3.3.0 and 5.1.0 are live!

The remaining part is a post-5.1.0 update #866

[yurnov]

Done