commit | 7e88b8e83cf15be58bdea5c70945ad2ecf3010fd | [log] [tgz] |
---|---|---|
author | renovate[bot] <29139614+renovate[bot]@users.noreply.github.com> | Fri Apr 19 22:53:39 2024 +0000 |
committer | GitHub <noreply@github.com> | Fri Apr 19 22:53:39 2024 +0000 |
tree | fc5213e91a6839f3a5d599517b04001c9681684d | |
parent | 6f8e8b4d04bc24e10ff7472fc8c7ffdd0607e5ad [diff] |
chore(deps): update module helm.sh/helm/v3 to v3.14.4 (#1111) This PR contains the following updates: Package Change Age Adoption Passing Confidence helm.sh/helm/v3 v3.14.2 -> v3.14.4 WarningSome dependencies could not be looked up. Check the warning logs for more information. Release Notes helm/helm (helm.sh/helm/v3) v3.14.4: Helm v3.14.4 Compare Source Helm v3.14.4 is a patch release. Users are encouraged to upgrade for the best experience. Users are encouraged to upgrade for the best experience. The community keeps growing, and we'd love to see you there! Join the discussion in Kubernetes Slack: for questions and just to hang out for discussing PRs, code, and bugs Hang out at the Public Developer Call: Thursday, 9:30 Pacific via Zoom Test, debug, and contribute charts: ArtifactHub/packages Installation and Upgrading Download Helm v3.14.4. The common platform binaries are here: MacOS amd64 (checksum / 73434aeac36ad068ce2e5582b8851a286dc628eae16494a26e2ad0b24a7199f9) MacOS arm64 (checksum / 61e9c5455f06b2ad0a1280975bf65892e707adc19d766b0cf4e9006e3b7b4b6c) Linux amd64 (checksum / a5844ef2c38ef6ddf3b5a8f7d91e7e0e8ebc39a38bb3fc8013d629c1ef29c259) Linux arm (checksum / 962297c944c06e1f275111a6e3d80e37c9e9e8fed967d4abec8efcf7fc9fb260) Linux arm64 (checksum / 113ccc53b7c57c2aba0cd0aa560b5500841b18b5210d78641acfddc53dac8ab2) Linux i386 (checksum / 2cb3ff032be1c39b7199b324d58d0ae05bc4fe49b9be6aa2fcbeb3fc03f1f9e7) Linux ppc64le (checksum / d0d625b43f6650ad376428520b2238baa2400bfedb43b2e0f24ad7247f0f59b5) Linux s390x (checksum / a5750d0cb1ba34ce84ab3be6382a14617130661d15dd2aa1b36630b293437936) Linux riscv64 (checksum / 925782b159392d52df5ebab88e04e695217325894c6a32a9a779e865b7e32411) Windows amd64 (checksum / 0b951db3eadd92dfe336b5a9ddb0640e5cd70d39abdbd7d3125e9fb59b22b669) This release was signed with 672C 657B E06B 4B30 969C 4A57 4614 49C2 5E36 B98E and can be found at @mattfarina keybase account. Please use the attached signatures for verifying this release using gpg. The Quickstart Guide will get you going from there. For upgrade instructions or detailed installation notes, check the install guide. You can also use a script to install on any system with bash. What's Next 3.15.0 is the next feature release and will be on May 08, 2024. Changelog refactor: create a helper for checking if a release is uninstalled 81c902a (Alex Petrov) fix: reinstall previously uninstalled chart with --keep-history 5a11c76 (Alex Petrov) chore: remove repetitive words fb3d880 (deterclosed) chore(deps): bump google.golang.org/protobuf from 1.31.0 to 1.33.0 01ac4a2 (dependabot[bot]) chore(deps): bump github.com/docker/docker 138602d (dependabot[bot]) bug: add proxy support for oci getter aa7d953 (Ricardo Maraschini) v3.14.3: Helm v3.14.3 Compare Source Helm v3.14.3 is a patch release. Users are encouraged to upgrade for the best experience. Users are encouraged to upgrade for the best experience. The community keeps growing, and we'd love to see you there! Join the discussion in Kubernetes Slack: for questions and just to hang out for discussing PRs, code, and bugs Hang out at the Public Developer Call: Thursday, 9:30 Pacific via Zoom Test, debug, and contribute charts: ArtifactHub/packages Installation and Upgrading Download Helm v3.14.3. The common platform binaries are here: MacOS amd64 (checksum / 4d5d01a94c7d6b07e71690dc1988bf3229680284c87f4242d28c6f1cc99653be) MacOS arm64 (checksum / dff794152b62b7c1a9ff615d510f8657bcd7a3727c668e0d9d4955f70d5f7573) Linux amd64 (checksum / 3c90f24e180f8c207b8a18e5ec82cb0fa49858a7a0a86e4ed52a98398681e00b) Linux arm (checksum / d4ff88f02d6731ec5dbde86a67bf391e673d0d9e87901727fbf62372aff106ec) Linux arm64 (checksum / 85e1573e76fa60af14ba7e9ec75db2129b6884203be866893fa0b3f7e41ccd5e) Linux i386 (checksum / af89e5df5cd21efe4dcaa478b19aaf17d22820716f93c1f098b00f1b7cfe1905) Linux ppc64le (checksum / aab121ca470e2a502cda849a9b3e92eeb9a32e213b0f0a79a95a04e375d26ce7) Linux s390x (checksum / d64fa8aced3244b549377741dc4e2db8109e5270c0723c11b547a9da5f99ad43) Linux riscv64 (checksum / f9f4e68bf43632f5df29e6c9fa760813d7e3537ed91d838cfdc2f103f8442b33) Windows amd64 (checksum / 369c6db1c114ef2a00793e9a587db6d7b2c72a23e37fd905c8deb78e9a8f7af6) This release was signed with 672C 657B E06B 4B30 969C 4A57 4614 49C2 5E36 B98E and can be found at @mattfarina keybase account. Please use the attached signatures for verifying this release using gpg. The Quickstart Guide will get you going from there. For upgrade instructions or detailed installation notes, check the install guide. You can also use a script to install on any system with bash. What's Next 3.14.4 will contain only bug fixes and be released on April 10, 2024. 3.15.0 is the next feature release and will be on May 08, 2024. Changelog Add a note about --dry-run displaying secrets f03cc04 (Matt Farina) add error messages 1a7330f (George Jenkins) Fix: Ignore alias validation error for index load d6acc00 (George Jenkins) chore(deps): bump github.com/containerd/containerd from 1.7.11 to 1.7.12 b2738fb (dependabot[bot]) chore(deps): bump github.com/DATA-DOG/go-sqlmock from 1.5.0 to 1.5.2 5b0847e (dependabot[bot]) Update architecture detection method 7e18c39 (weidongkl) Configuration 📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined). 🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied. ♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox. 🔕 Ignore: Close this PR and you won't be reminded about this update again. If you want to rebase/retry this PR, check this box This PR has been generated by Mend Renovate. View repository job log here.
If you have any questions and discussions about Atmosphere, you can join the community:
#atmosphere
channel on the Kubernetes Slack. If you are new to Kubernetes Slack workspace, Join the Kubernetes Slack workspace first.The quick start intends to provide the most near-production experience possible, as it is architected purely towards production-only environments. In order to get a quick production-ready experience of Atmosphere, you will need access to an OpenStack cloud.
The quick start is powered by Molecule and it is used in continuous integration running against the VEXXHOST public cloud so that would be an easy target to use to try it out.
You will need the following quotas set up in your cloud account:
These resources will be used to create a total of 8 instances broken up as follows:
First of all, you'll have to make sure you clone the repository locally to your system with git
by running the following command:
git clone https://github.com/vexxhost/atmosphere
You will need poetry
installed on your operating system. You will need to make sure that you have the appropriate OpenStack environment variables set (such as OS_CLOUD
or OS_AUTH_URL
, etc.). You can also use the following environment variables to tweak the behaviour of the Heat stack that is created:
ATMOSPHERE_STACK_NAME
: The name of the Heat stack to be created (defaults to atmosphere
).
ATMOSPHERE_PUBLIC_NETWORK
: The name of the public network to attach floating IPs from (defaults to public
).
ATMOSPHERE_IMAGE
: The name or UUID of the image to be used for deploying the instances (defaults to Ubuntu 20.04.3 LTS (x86_64) [2021-10-04]
).
ATMOSPHERE_INSTANCE_TYPE
(Deprecated): The instance type used to deploy all of the different instances.(It doesn't have its own default value.) This has been deprecated from v1.4.0. You can configure the instance type per a machine role using ATMOSPHERE_CONTROLLER_INSTANCE_TYPE
, ATMOSPHERE_COMPUTE_INSTANCE_TYPE
, and ATMOSPHERE_STORAGE_INSTANCE_TYPE
variables. For backwards compatibility, if variables specific to the machine roles are not set and ATMOSPHERE_INSTANCE_TYPE
is set, ATMOSPHERE_INSTANCE_TYPE
value is used.
ATMOSPHERE_CONTROLLER_INSTANCE_TYPE
: The instance type used to deploy controller instances (defaults to v3-standard-16
).
ATMOSPHERE_COMPUTE_INSTANCE_TYPE
: The instance type used to deploy compute instances (defaults to v3-standard-4
).
ATMOSPHERE_STORAGE_INSTANCE_TYPE
: The instance type used to deploy storage instances (defaults to v3-standard-4
).
ATMOSPHERE_NAMESERVERS
: A comma-separated list of nameservers to be used for the instances (defaults to 1.1.1.1
).
ATMOSPHERE_USERNAME
: The username what is used to login into the instances ( defaults to ubuntu
).
ATMOSPHERE_DNS_SUFFIX_NAME
: The DNS domainname that is used for the API and Horizon. (defaults to nip.io
).
ATMOSPHERE_ACME_SERVER
: The ACME server, currenly this is from LetsEncrypt, with StepCA from SmallStep it is possible to run a internal ACME server. The CA of that ACME server should be present in the instance image.
ATMOSPHERE_ANSIBLE_VARS_PATH
: The path for ansible group_vars and host_vars. This to build a multinode development cluster with own configs, that are not generated by molecule. This way you can test your configs before you bring them to production.
Once you're ready to get started, you can run the following command to install poetry dependencies:
poetry install
Then you can run the following command to build the Heat stack :
poetry run molecule converge
This will create a Heat stack with the name atmosphere
and start deploying the cloud. Once it's complete, you can login to any of the systems by using the login
sub-command. For exampel, to login to the first controller node, you can run the following:
poetry run molecule login -h ctl1
In all the controllers, you will find an openrc
file location inside the root
account home directory, as well as the OpenStack client installed there as well. You can use it by running the following after logging in:
source /root/openrc openstack server list
The Kubernetes administrator configuration will also be available on all of the control plane nodes, you can simply use it by running kubectl
commands on any of the controllers as root
:
kubectl get nodes -owide
Once you're done with your environment and you need to tear it down, you can use the destroy
sub-command:
poetry run molecule destroy
For more information about the different commands used by Molecule, you can refer to the Molecule documentation.
You'll need to make sure that you have pre-commit
setup and installed in your environment by running these commands:
pre-commit install --hook-type commit-msg