Migrate to the community-hosted package repositories (pkgs.k8s.io) and to dl.k8s.io

[xmudrii]

What this PR does / why we need it:

There are three changes introduced in this PR:

• Migrate to the community-hosted package repositories (pkgs.k8s.io) from the deprecated Google-hosted package repository (apt.kubernetes.io and yum.kubernetes.io)
  • The Kubernetes project strongly encourages and recommends migrating to the new package repositories as soon as possible
  • Given that the Google-hosted repository is deprecated, I decided to do unconditional migration, i.e. without giving an option to opt-out from this change. This is going to make it easier for us to maintain and support this release branch in the long term. Moreover, most users are not going to notice this change at all. This change might only affect users allowlisting traffic based on IP addresses or URLs, in which case they need to update their allowlists (this is explained in the release note)
• Migrate to dl.k8s.io instead of pulling binaries from the release bucket directly
• The kubernetes-release bucket might get deprecated and frozen in the future as part of efforts to migrate to the community-owned infrastructure. The Kubernetes project strongly recommends using dl.k8s.io going forward
• Same as the previous change, this change shouldn't affect many users. Additionally, this only affects Flatcar-based clusters. Users using allowlisting might need to update their configuration and this is explained in the release note
• cri-tools is updated to v1.27.1 for clusters running Kubernetes 1.27. Kubernetes 1.28 clusters will use cri-tools v1.28.0

Additionally, tests are updated to use KubeOne 1.6 as the stable version for initially provisioning the cluster.

Which issue(s) this PR fixes:
Fixes #2870

What type of PR is this?

/kind feature

Does this PR introduce a user-facing change? Then add your Release Note here:

- [ACTION REQUIRED] Migrate from the legacy package repositories (`apt.kubernetes.io` and `yum.kubernetes.io`) to the Kubernetes community-hosted package repositories (`pkgs.k8s.io`). The legacy repositories [have been deprecated as of August 31, 2023 and will be frozen starting from September 13, 2023](https://kubernetes.io/blog/2023/08/31/legacy-package-repository-deprecation/). Upgrading to KubeOne v1.7.0+ or v1.6.3+ is required in order to install or upgrade to Kubernetes version newer than v1.27.6, v1.26.9, and v1.25.14. **If IP-based or URL-based filtering is in place**, you may need to mirror the release packages to a local package repository that you have strict control over. See [the official announcement](https://kubernetes.io/blog/2023/08/15/pkgs-k8s-io-introduction/) for more details
- [ACTION REQUIRED] Migrate from the Kubernetes release bucket (`https://storage.googleapis.com/kubernetes-release/release`) to `dl.k8s.io` for downloading binaries. This change only affects Flatcar-based clusters. **If IP-based or URL-based filtering is in place**, you need to allow the appropriate IP addresses and domains as described in [the official `dl.k8s.io` announcement](https://kubernetes.io/blog/2023/06/09/dl-adopt-cdn/)
- Upgrade cri-tools to v1.27.1 for clusters running Kubernetes 1.27

Documentation:

TBD

(this should be mentioned in the upgrade guide)

[kubermatic-bot]

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

[xmudrii]

/cherrypick release/v1.6

[kubermatic-bot]

@xmudrii: once the present PR merges, I will cherry-pick it on top of release/v1.6 in a new PR and assign it to you.

In response to this:

/cherrypick release/v1.6

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.

[xmudrii]

/test pull-kubeone-e2e-aws-amzn-install-containerd-external-v1.27.3
/test pull-kubeone-e2e-aws-centos-install-containerd-external-v1.27.3
/test pull-kubeone-e2e-aws-default-install-containerd-external-v1.27.3
/test pull-kubeone-e2e-aws-flatcar-install-containerd-external-v1.27.3

[xmudrii]

/test pull-kubeone-e2e-aws-rhel-install-containerd-external-v1.27.3
/test pull-kubeone-e2e-aws-rockylinux-install-containerd-external-v1.27.3

[xmudrii]

/test pull-kubeone-e2e-azure-centos-install-containerd-external-v1.27.3
/test pull-kubeone-e2e-azure-default-install-containerd-external-v1.27.3
/test pull-kubeone-e2e-azure-rhel-install-containerd-external-v1.27.3

[xmudrii]

/test pull-kubeone-e2e-azure-flatcar-install-containerd-external-v1.27.3
/test pull-kubeone-e2e-azure-rockylinux-install-containerd-external-v1.27.3
/test pull-kubeone-e2e-openstack-default-install-containerd-external-v1.27.3

[kron4eg]

/lgtm

[kubermatic-bot]

LGTM label has been added.

Git tree hash: e4739a969a6f3f4d12096dd8b62495e43a3a3e2a

[kron4eg]

/approve

[kron4eg]

/retest

[kron4eg]

/retest

[xmudrii]

/test pull-kubeone-e2e-aws-amzn-stable-upgrade-containerd-external-from-v1.26.6-to-v1.27.3
/test pull-kubeone-e2e-aws-centos-stable-upgrade-containerd-external-from-v1.26.6-to-v1.27.3
/test pull-kubeone-e2e-aws-default-stable-upgrade-containerd-external-from-v1.26.6-to-v1.27.3

[kubermatic-bot]

LGTM label has been added.

Git tree hash: 806fb5c7b485a40ba70c6cd890e963cbfeb306b2

[xmudrii]

/test pull-kubeone-e2e-aws-centos-stable-upgrade-containerd-external-from-v1.26.6-to-v1.27.3

[xmudrii]

/test pull-kubeone-e2e-aws-amzn-stable-upgrade-containerd-external-from-v1.26.6-to-v1.27.3
/test pull-kubeone-e2e-aws-centos-stable-upgrade-containerd-external-from-v1.26.6-to-v1.27.3

[xmudrii]

/test pull-kubeone-e2e-aws-rhel-stable-upgrade-containerd-external-from-v1.26.6-to-v1.27.3
/test pull-kubeone-e2e-aws-rockylinux-stable-upgrade-containerd-external-from-v1.26.6-to-v1.27.3
/test pull-kubeone-e2e-aws-default-stable-upgrade-containerd-external-from-v1.26.6-to-v1.27.3
/test pull-kubeone-e2e-aws-flatcar-stable-upgrade-containerd-external-from-v1.26.6-to-v1.27.3

[xmudrii]

/test pull-kubeone-e2e-openstack-centos-stable-upgrade-containerd-external-from-v1.26.6-to-v1.27.3

[kubermatic-bot]

@xmudrii: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
pull-kubeone-e2e-openstack-default-install-containerd-external-v1.27.3	8a5e4c9	link	true	/test pull-kubeone-e2e-openstack-default-install-containerd-external-v1.27.3

Full PR test history

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.

[xmudrii]

/retest

[ahmedwaleedmalik]

/approve

[kubermatic-bot]

LGTM label has been added.

Git tree hash: 2fc65a7875fdbbd6058189b56a37fd0f4bdeb580

[kubermatic-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ahmedwaleedmalik, kron4eg

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

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [ahmedwaleedmalik,kron4eg]

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

[kubermatic-bot]

@xmudrii: #2873 failed to apply on top of branch "release/v1.6":

Applying: Migrate to pkgs.k8s.io
Applying: Migrate to dl.k8s.io
Applying: Update fixtures
Applying: Use release/v1.6 as a stable version for upgrade tests
Using index info to reconstruct a base tree...
M	test/e2e/prow.yaml
M	test/e2e/scenario_upgrade.go
M	test/tests.yml
Falling back to patching base and 3-way merge...
Auto-merging test/tests.yml
CONFLICT (content): Merge conflict in test/tests.yml
Auto-merging test/e2e/scenario_upgrade.go
Auto-merging test/e2e/prow.yaml
CONFLICT (content): Merge conflict in test/e2e/prow.yaml
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0004 Use release/v1.6 as a stable version for upgrade tests
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".

In response to this:

/cherrypick release/v1.6

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.