clank/kubernetes-init
1
0
Fork 0
Code Issues 1 Pull Requests Projects Releases Wiki Activity

Update all dependencies #7

Merged
kjuulh merged 1 commits from renovate/all into main 2023-02-28 18:26:19 +01:00
Conversation 0 Commits 1 Files Changed 2 +2 -2
kjuulh commented 2023-01-10 21:58:28 +01:00
Owner
Copy Link

This PR contains the following updates:

Package Type Update Change
cloudflare (source) required_provider major ~> 3.0 -> ~> 4.0
flux (source) required_provider minor 0.22.2 -> 0.24.2

Release Notes

cloudflare/terraform-provider-cloudflare

v4.0.0

Compare Source

Warning

Prior to upgrading you should ensure you have adequate backups in the event you need to rollback to version 3. This is a major version bump and involves backwards incompatible changes.

3.x to 4.x upgrade guide

BREAKING CHANGES:

  • datasource/cloudflare_waf_groups: removed in favour of cloudflare_rulesets (#​2138)
  • datasource/cloudflare_waf_packages: removed in favour of cloudflare_rulesets (#​2138)
  • datasource/cloudflare_waf_rules: removed in favour of cloudflare_rulesets (#​2138)
  • provider: account_id is no longer available as a global configuration option. Instead, use the resource specific attributes. (#​2139)
  • resource/cloudflare_access_bookmark: resource has been removed in favour of configuration on cloudflare_access_application (#​2136)
  • resource/cloudflare_access_rule: require explicit zone_id or account_id and remove implicit fallback to user level rules (#​2157)
  • resource/cloudflare_account_member: account_id is now required (#​2153)
  • resource/cloudflare_account_member: no longer sets client.AccountID internally and relies on the resource provided value (#​2154)
  • resource/cloudflare_argo_tunnel: resource has been renamed to cloudflare_tunnel (#​2135)
  • resource/cloudflare_ip_list: removed in favour of cloudflare_list (#​2137)
  • resource/cloudflare_load_balancer: Migrate session_affinity_attributes from TypeMap to TypeSet (#​1959)
  • resource/cloudflare_load_balancer: session_affinity_attributes.drain_duration is now TypeInt instead of TypeString (#​1959)
  • resource/cloudflare_load_balancer_monitor: account_id is now required (#​2153)
  • resource/cloudflare_load_balancer_monitor: no longer sets client.AccountID internally and relies on the resource provided value (#​2154)
  • resource/cloudflare_load_balancer_pool: account_id is now required (#​2153)
  • resource/cloudflare_load_balancer_pool: no longer sets client.AccountID internally and relies on the resource provided value (#​2154)
  • resource/cloudflare_spectrum_application: edge_ip_connectivity is now nested under edge_ips as connectivity (#​2219)
  • resource/cloudflare_spectrum_application: edge_ips.type is now a required field (#​2219)
  • resource/cloudflare_spectrum_application: edge_ips now contains nested attributes other than IP ranges. type and connectivity have been added. edge_ips.ips contains the static IP addresses that used to reside at edge_ips. (#​2219)
  • resource/cloudflare_waf_group: removed in favour of cloudflare_ruleset (#​2138)
  • resource/cloudflare_waf_override: removed in favour of cloudflare_ruleset (#​2138)
  • resource/cloudflare_waf_package: removed in favour of cloudflare_ruleset (#​2138)
  • resource/cloudflare_waf_rule: removed in favour of cloudflare_ruleset (#​2138)
  • resource/cloudflare_workers_kv: account_id is now required (#​2153)
  • resource/cloudflare_workers_kv: no longer sets client.AccountID internally and relies on the resource provided value (#​2154)
  • resource/cloudflare_workers_kv_namespace: account_id is now required (#​2153)
  • resource/cloudflare_workers_kv_namespace: no longer sets client.AccountID internally and relies on the resource provided value (#​2154)
  • resource/cloudflare_workers_script: account_id is now required (#​2153)
  • resource/cloudflare_workers_script: no longer sets client.AccountID internally and relies on the resource provided value (#​2154)
  • resource/cloudflare_zone: account_id is now required (#​2153)
  • resource/cloudflare_zone: no longer sets client.AccountID internally and relies on the resource provided value (#​2154)
fluxcd/terraform-provider-flux

v0.24.2

Compare Source

Release date: 2023-02-28

This prerelease includes flux2 v0.40.2.

v0.24.1

Compare Source

Release date: 2023-02-23

This prerelease includes flux2 v0.40.1.

v0.24.0

Compare Source

Release date: 2023-02-20

This prerelease includes flux2 v0.40.0.

This release contains a breaking change with the removal of the git_implementation attribute from the flux_sync data source. The libgit2 implementation has been removed from Flux as the go-git implementation supports all Git servers, including Azure DevOps and AWS CodeCommit.

Some minor fixes have been made to the new flux_bootstrap_git resource as users were experiencing issues setting custom components configuration.

v0.23.0

Compare Source

Release date: 2023-02-02

This prerelease includes flux2 v0.39.0.

A new resource flux_bootstrap_git has been added as a replacement to the current two data source.

Bootstrapping Flux with Terraform has been a feature that was available early on in Fluxcd V2 development. With time new features in Flux and more requirements from end users have made the experience complex and error-prone.
A big reason is that the solution was built with a focus on using existing providers to manage the interaction with Git and Kubernetes. While it saved time early on it caused issues in the long run.
Flux has specific requirements in the order resources are applied and removed to work properly, which became very difficult to express with Terraform. In the worst case, Terraform would not be able to run at all due to the dependency complexity.

Over the last couple of months, a new provider resource has been developed to replace the old bootstrapping method. The resource implements all the functionality required to bootstrap Flux, removing the dependency on third-party Terraform providers.
The goal has been to replicate the features offered by the Flux CLI as close as possible while solving long-standing issues current users experience with the provider.

Currently customizing the Flux installation has issues as it only affects how Flux reconciles itself but now how the manifests are applied to Kubernetes. This results in issues for the end user as their cluster may block Pods lacking specific security settings.
This issue is no longer present in the new solution as the provider manages both the process of committing the customized configuration to Git and applying it to Kubernetes.

Another long-standing issue has been uninstalling Flux with Terraform. The old solution was for the most part luck based if the resources were removed in the right order and enough time was allowed for finalizers to be removed by the Flux controllers.
This rarely occurred causing clusters to be stuck in locked states. The new solution will always remove resources in the correct order, making sure that all finalizers are removed before Kubernetes considers the resource to be fully removed from Terraform.

The plan forward is to only work on developing the new Terraform resource, initially focusing on ironing out any early bugs. While the new resource is stable there may occur some breaking attribute changes to deal with unforeseen use cases. While having said that feedback
is needed to make the Terraform experience with Flux better, so please start evaluating the new Terraform resource. A migration guide is available which walks through the step-by-step process for how to migrate between the old and new solution without breaking an existing Flux installation.
When the attributes in the new resource are considered set, the old data sources will be deprecated, and eventually removed. Until then it is recommended to start looking at which features are missing in the new resource to cover specific use cases.

v0.22.3

Compare Source

Release date: 2023-01-10

This prerelease includes flux2 v0.38.3.

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

  • If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

This PR contains the following updates: | Package | Type | Update | Change | |---|---|---|---| | [cloudflare](https://registry.terraform.io/providers/cloudflare/cloudflare) ([source](https://github.com/cloudflare/terraform-provider-cloudflare)) | required_provider | major | `~> 3.0` -> `~> 4.0` | | [flux](https://registry.terraform.io/providers/fluxcd/flux) ([source](https://github.com/fluxcd/terraform-provider-flux)) | required_provider | minor | `0.22.2` -> `0.24.2` | --- ### Release Notes <details> <summary>cloudflare/terraform-provider-cloudflare</summary> ### [`v4.0.0`](https://github.com/cloudflare/terraform-provider-cloudflare/blob/HEAD/CHANGELOG.md#&#8203;400-February-21st-2023) [Compare Source](https://github.com/cloudflare/terraform-provider-cloudflare/compare/v3.35.0...v4.0.0) > **Warning** Prior to upgrading you should ensure you have adequate backups in the event you need to rollback to version 3. This is a major version bump and involves backwards incompatible changes. [3.x to 4.x upgrade guide](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs/guides/version-4-upgrade) BREAKING CHANGES: - datasource/cloudflare_waf_groups: removed in favour of `cloudflare_rulesets` ([#&#8203;2138](https://github.com/cloudflare/terraform-provider-cloudflare/issues/2138)) - datasource/cloudflare_waf_packages: removed in favour of `cloudflare_rulesets` ([#&#8203;2138](https://github.com/cloudflare/terraform-provider-cloudflare/issues/2138)) - datasource/cloudflare_waf_rules: removed in favour of `cloudflare_rulesets` ([#&#8203;2138](https://github.com/cloudflare/terraform-provider-cloudflare/issues/2138)) - provider: `account_id` is no longer available as a global configuration option. Instead, use the resource specific attributes. ([#&#8203;2139](https://github.com/cloudflare/terraform-provider-cloudflare/issues/2139)) - resource/cloudflare_access_bookmark: resource has been removed in favour of configuration on `cloudflare_access_application` ([#&#8203;2136](https://github.com/cloudflare/terraform-provider-cloudflare/issues/2136)) - resource/cloudflare_access_rule: require explicit `zone_id` or `account_id` and remove implicit fallback to user level rules ([#&#8203;2157](https://github.com/cloudflare/terraform-provider-cloudflare/issues/2157)) - resource/cloudflare_account_member: `account_id` is now required ([#&#8203;2153](https://github.com/cloudflare/terraform-provider-cloudflare/issues/2153)) - resource/cloudflare_account_member: no longer sets `client.AccountID` internally and relies on the resource provided value ([#&#8203;2154](https://github.com/cloudflare/terraform-provider-cloudflare/issues/2154)) - resource/cloudflare_argo_tunnel: resource has been renamed to `cloudflare_tunnel` ([#&#8203;2135](https://github.com/cloudflare/terraform-provider-cloudflare/issues/2135)) - resource/cloudflare_ip_list: removed in favour of `cloudflare_list` ([#&#8203;2137](https://github.com/cloudflare/terraform-provider-cloudflare/issues/2137)) - resource/cloudflare_load_balancer: Migrate session_affinity_attributes from TypeMap to TypeSet ([#&#8203;1959](https://github.com/cloudflare/terraform-provider-cloudflare/issues/1959)) - resource/cloudflare_load_balancer: `session_affinity_attributes.drain_duration` is now `TypeInt` instead of `TypeString` ([#&#8203;1959](https://github.com/cloudflare/terraform-provider-cloudflare/issues/1959)) - resource/cloudflare_load_balancer_monitor: `account_id` is now required ([#&#8203;2153](https://github.com/cloudflare/terraform-provider-cloudflare/issues/2153)) - resource/cloudflare_load_balancer_monitor: no longer sets `client.AccountID` internally and relies on the resource provided value ([#&#8203;2154](https://github.com/cloudflare/terraform-provider-cloudflare/issues/2154)) - resource/cloudflare_load_balancer_pool: `account_id` is now required ([#&#8203;2153](https://github.com/cloudflare/terraform-provider-cloudflare/issues/2153)) - resource/cloudflare_load_balancer_pool: no longer sets `client.AccountID` internally and relies on the resource provided value ([#&#8203;2154](https://github.com/cloudflare/terraform-provider-cloudflare/issues/2154)) - resource/cloudflare_spectrum_application: `edge_ip_connectivity` is now nested under `edge_ips` as `connectivity` ([#&#8203;2219](https://github.com/cloudflare/terraform-provider-cloudflare/issues/2219)) - resource/cloudflare_spectrum_application: `edge_ips.type` is now a required field ([#&#8203;2219](https://github.com/cloudflare/terraform-provider-cloudflare/issues/2219)) - resource/cloudflare_spectrum_application: `edge_ips` now contains nested attributes other than IP ranges. `type` and `connectivity` have been added. `edge_ips.ips` contains the static IP addresses that used to reside at `edge_ips`. ([#&#8203;2219](https://github.com/cloudflare/terraform-provider-cloudflare/issues/2219)) - resource/cloudflare_waf_group: removed in favour of `cloudflare_ruleset` ([#&#8203;2138](https://github.com/cloudflare/terraform-provider-cloudflare/issues/2138)) - resource/cloudflare_waf_override: removed in favour of `cloudflare_ruleset` ([#&#8203;2138](https://github.com/cloudflare/terraform-provider-cloudflare/issues/2138)) - resource/cloudflare_waf_package: removed in favour of `cloudflare_ruleset` ([#&#8203;2138](https://github.com/cloudflare/terraform-provider-cloudflare/issues/2138)) - resource/cloudflare_waf_rule: removed in favour of `cloudflare_ruleset` ([#&#8203;2138](https://github.com/cloudflare/terraform-provider-cloudflare/issues/2138)) - resource/cloudflare_workers_kv: `account_id` is now required ([#&#8203;2153](https://github.com/cloudflare/terraform-provider-cloudflare/issues/2153)) - resource/cloudflare_workers_kv: no longer sets `client.AccountID` internally and relies on the resource provided value ([#&#8203;2154](https://github.com/cloudflare/terraform-provider-cloudflare/issues/2154)) - resource/cloudflare_workers_kv_namespace: `account_id` is now required ([#&#8203;2153](https://github.com/cloudflare/terraform-provider-cloudflare/issues/2153)) - resource/cloudflare_workers_kv_namespace: no longer sets `client.AccountID` internally and relies on the resource provided value ([#&#8203;2154](https://github.com/cloudflare/terraform-provider-cloudflare/issues/2154)) - resource/cloudflare_workers_script: `account_id` is now required ([#&#8203;2153](https://github.com/cloudflare/terraform-provider-cloudflare/issues/2153)) - resource/cloudflare_workers_script: no longer sets `client.AccountID` internally and relies on the resource provided value ([#&#8203;2154](https://github.com/cloudflare/terraform-provider-cloudflare/issues/2154)) - resource/cloudflare_zone: `account_id` is now required ([#&#8203;2153](https://github.com/cloudflare/terraform-provider-cloudflare/issues/2153)) - resource/cloudflare_zone: no longer sets `client.AccountID` internally and relies on the resource provided value ([#&#8203;2154](https://github.com/cloudflare/terraform-provider-cloudflare/issues/2154)) </details> <details> <summary>fluxcd/terraform-provider-flux</summary> ### [`v0.24.2`](https://github.com/fluxcd/terraform-provider-flux/blob/HEAD/CHANGELOG.md#&#8203;0242) [Compare Source](https://github.com/fluxcd/terraform-provider-flux/compare/v0.24.1...v0.24.2) **Release date:** 2023-02-28 This prerelease includes flux2 [v0.40.2](https://github.com/fluxcd/flux2/releases/tag/v0.40.2). ### [`v0.24.1`](https://github.com/fluxcd/terraform-provider-flux/blob/HEAD/CHANGELOG.md#&#8203;0241) [Compare Source](https://github.com/fluxcd/terraform-provider-flux/compare/v0.24.0...v0.24.1) **Release date:** 2023-02-23 This prerelease includes flux2 [v0.40.1](https://github.com/fluxcd/flux2/releases/tag/v0.40.1). ### [`v0.24.0`](https://github.com/fluxcd/terraform-provider-flux/blob/HEAD/CHANGELOG.md#&#8203;0240) [Compare Source](https://github.com/fluxcd/terraform-provider-flux/compare/v0.23.0...v0.24.0) **Release date:** 2023-02-20 This prerelease includes flux2 [v0.40.0](https://github.com/fluxcd/flux2/releases/tag/v0.40.0). This release contains a breaking change with the removal of the `git_implementation` attribute from the `flux_sync` data source. The libgit2 implementation has been removed from Flux as the `go-git` implementation supports all Git servers, including Azure DevOps and AWS CodeCommit. Some minor fixes have been made to the new `flux_bootstrap_git` resource as users were experiencing issues setting custom components configuration. ### [`v0.23.0`](https://github.com/fluxcd/terraform-provider-flux/blob/HEAD/CHANGELOG.md#&#8203;0230) [Compare Source](https://github.com/fluxcd/terraform-provider-flux/compare/v0.22.3...v0.23.0) **Release date:** 2023-02-02 This prerelease includes flux2 [v0.39.0](https://github.com/fluxcd/flux2/releases/tag/v0.39.0). A new resource `flux_bootstrap_git` has been added as a replacement to the current two data source. Bootstrapping Flux with Terraform has been a feature that was available early on in Fluxcd V2 development. With time new features in Flux and more requirements from end users have made the experience complex and error-prone. A big reason is that the solution was built with a focus on using existing providers to manage the interaction with Git and Kubernetes. While it saved time early on it caused issues in the long run. Flux has specific requirements in the order resources are applied and removed to work properly, which became very difficult to express with Terraform. In the worst case, Terraform would not be able to run at all due to the dependency complexity. Over the last couple of months, a new provider resource has been developed to replace the old bootstrapping method. The resource implements all the functionality required to bootstrap Flux, removing the dependency on third-party Terraform providers. The goal has been to replicate the features offered by the Flux CLI as close as possible while solving long-standing issues current users experience with the provider. Currently customizing the Flux installation has issues as it only affects how Flux reconciles itself but now how the manifests are applied to Kubernetes. This results in issues for the end user as their cluster may block Pods lacking specific security settings. This issue is no longer present in the new solution as the provider manages both the process of committing the customized configuration to Git and applying it to Kubernetes. Another long-standing issue has been uninstalling Flux with Terraform. The old solution was for the most part luck based if the resources were removed in the right order and enough time was allowed for finalizers to be removed by the Flux controllers. This rarely occurred causing clusters to be stuck in locked states. The new solution will always remove resources in the correct order, making sure that all finalizers are removed before Kubernetes considers the resource to be fully removed from Terraform. The plan forward is to only work on developing the new Terraform resource, initially focusing on ironing out any early bugs. While the new resource is stable there may occur some breaking attribute changes to deal with unforeseen use cases. While having said that feedback is needed to make the Terraform experience with Flux better, so please start evaluating the new Terraform resource. A migration guide is available which walks through the step-by-step process for how to migrate between the old and new solution without breaking an existing Flux installation. When the attributes in the new resource are considered set, the old data sources will be deprecated, and eventually removed. Until then it is recommended to start looking at which features are missing in the new resource to cover specific use cases. ### [`v0.22.3`](https://github.com/fluxcd/terraform-provider-flux/blob/HEAD/CHANGELOG.md#&#8203;0223) [Compare Source](https://github.com/fluxcd/terraform-provider-flux/compare/v0.22.2...v0.22.3) **Release date:** 2023-01-10 This prerelease includes flux2 [v0.38.3](https://github.com/fluxcd/flux2/releases/tag/v0.38.3). </details> --- ### Configuration 📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Enabled. ♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox. 👻 **Immortal**: This PR will be recreated if closed unmerged. Get [config help](https://github.com/renovatebot/renovate/discussions) if that's undesired. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Renovate Bot](https://github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzNC45Ny40IiwidXBkYXRlZEluVmVyIjoiMzQuMTU0LjAifQ==-->
kjuulh force-pushed renovate/all from 20ac984d01 to 897c8ff1ac 2023-02-02 21:02:14 +01:00 Compare
kjuulh changed title from Update Terraform flux to v0.22.3 to Update Terraform flux to v0.23.0 2023-02-02 21:02:14 +01:00
kjuulh force-pushed renovate/all from 897c8ff1ac to d311be42aa 2023-02-21 15:47:28 +01:00 Compare
kjuulh changed title from Update Terraform flux to v0.23.0 to Update all dependencies 2023-02-21 15:47:29 +01:00
kjuulh force-pushed renovate/all from d311be42aa to c5ae92a1a8 2023-02-23 20:48:40 +01:00 Compare
kjuulh force-pushed renovate/all from c5ae92a1a8 to b3a09f81c4 2023-02-28 18:04:36 +01:00 Compare
kjuulh merged commit b3a09f81c4 into main 2023-02-28 18:26:19 +01:00
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No Label
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: clank/kubernetes-init#7
No description provided.
Delete Branch "renovate/all"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?