Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix namespace requirement in template metadata #2387

Merged
merged 6 commits into from
Jan 8, 2024

Conversation

arybolovlev
Copy link
Contributor

@arybolovlev arybolovlev commented Jan 5, 2024

Description

This PR fix an issue when the provider forces a resource recreation after upgrading to 2.25.0 and 2.25.1 due to changes in the schema of the following resources:

  • kubernetes_stateful_set_v1
  • kubernetes_stateful_set
  • kubernetes_daemon_set_v1
  • kubernetes_daemonset
  • kubernetes_cron_job_v1
  • kubernetes_cron_job

Resources kubernetes_stateful_set_v1, kubernetes_stateful_set, kubernetes_daemon_set_v1, and kubernetes_daemonset got a new attribute spec.template.metadata.namespace. It is a stub attribute that does not affect the namespace in which the Pod will be created. The Pod will be created in the same namespace as the main resource. However, modifying this field will force the resource recreation.

Resources kubernetes_cron_job_v1 and kubernetes_cron_job got a new attribute spec.job_template.metadata.namespace. It is a stub attribute that does not affect the namespace in which the Pod will be created. The Pod will be created in the same namespace as the main resource. However, modifying this field will force the resource recreation.

Acceptance tests

  • Have you added an acceptance test for the functionality being added?
  • Have you run the acceptance tests on this branch?

References

Community Note

  • Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment

@arybolovlev arybolovlev marked this pull request as ready for review January 5, 2024 13:13
@arybolovlev arybolovlev requested a review from a team as a code owner January 5, 2024 13:13
@arybolovlev arybolovlev merged commit 06d0a07 into main Jan 8, 2024
16 checks passed
@arybolovlev arybolovlev deleted the hotfix-namespace-requirement branch January 8, 2024 08:11
dduportal referenced this pull request in jenkins-infra/azure Jan 9, 2024
<Actions>
<action
id="bcd9b70d7c1eb1e07eb5ad8a958f18dc1bbd81461ee1a2604adeea46e3148a47">
        <h3>Bump Terraform `kubernetes` provider version</h3>
<details
id="1d9343c012f5434ac9fe8a98135bae3667b399259be16d9b14302ea3bd424a24">
            <summary>Update Terraform lock file</summary>
<p>&#34;hashicorp/kubernetes&#34; updated from &#34;2.25.1&#34; to
&#34;2.25.2&#34; in file &#34;.terraform.lock.hcl&#34;</p>
            <details>
                <summary>2.25.2</summary>
<pre>Changelog retrieved
from:&#xA;&#x9;https://github.com/hashicorp/terraform-provider-kubernetes/releases/tag/v2.25.2&#xA;BUG
FIXES:&#xA;&#xA;* `resource/kubernetes_cron_job_v1`: fix an issue when
the provider forces a resource recreation after upgrading to `2.25.0`
and `2.25.1` due to changes in the resource schema.
[[GH-2387](https://github.com/hashicorp/terraform-provider-kubernetes/issues/2387)]&#xA;*
`resource/kubernetes_cron_job`: fix an issue when the provider forces a
resource recreation after upgrading to `2.25.0` and `2.25.1` due to
changes in the resource schema.
[[GH-2387](https://github.com/hashicorp/terraform-provider-kubernetes/issues/2387)]&#xA;*
`resource/kubernetes_daemon_set_v1`: fix an issue when the provider
forces a resource recreation after upgrading to `2.25.0` and `2.25.1`
due to changes in the resource schema.
[[GH-2387](https://github.com/hashicorp/terraform-provider-kubernetes/issues/2387)]&#xA;*
`resource/kubernetes_daemonset`: fix an issue when the provider forces a
resource recreation after upgrading to `2.25.0` and `2.25.1` due to
changes in the resource schema.
[[GH-2387](https://github.com/hashicorp/terraform-provider-kubernetes/issues/2387)]&#xA;*
`resource/kubernetes_stateful_set_v1`: fix an issue when the provider
forces a resource recreation after upgrading to `2.25.0` and `2.25.1`
due to changes in the resource schema.
[[GH-2387](https://github.com/hashicorp/terraform-provider-kubernetes/issues/2387)]&#xA;*
`resource/kubernetes_stateful_set`: fix an issue when the provider
forces a resource recreation after upgrading to `2.25.0` and `2.25.1`
due to changes in the resource schema.
[[GH-2387](https://github.com/hashicorp/terraform-provider-kubernetes/issues/2387)]&#xA;&#xA;NOTES:&#xA;&#xA;*
Resources `kubernetes_cron_job_v1` and `kubernetes_cron_job` got a new
attribute `spec.job_template.metadata.namespace`. It is a stub attribute
that does not affect the namespace in which the Pod will be created. The
Pod will be created in the same namespace as the main resource. However,
modifying this field will force the resource recreation.
[[GH-2387](https://github.com/hashicorp/terraform-provider-kubernetes/issues/2387)]&#xA;*
Resources `kubernetes_stateful_set_v1`, `kubernetes_stateful_set`,
`kubernetes_daemon_set_v1`, and `kubernetes_daemonset` got a new
attribute `spec.template.metadata.namespace`. It is a stub attribute
that does not affect the namespace in which the Pod will be created. The
Pod will be created in the same namespace as the main resource. However,
modifying this field will force the resource recreation.
[[GH-2387](https://github.com/hashicorp/terraform-provider-kubernetes/issues/2387)]&#xA;&#xA;&#xA;</pre>
            </details>
        </details>
<a
href="https://infra.ci.jenkins.io/job/terraform-jobs/job/azure/job/main/996/">Jenkins
pipeline link</a>
    </action>
</Actions>

---

<table>
  <tr>
    <td width="77">
<img src="https://www.updatecli.io/images/updatecli.png" alt="Updatecli
logo" width="50" height="50">
    </td>
    <td>
      <p>
Created automatically by <a
href="https://www.updatecli.io/">Updatecli</a>
      </p>
      <details><summary>Options:</summary>
        <br />
<p>Most of Updatecli configuration is done via <a
href="https://www.updatecli.io/docs/prologue/quick-start/">its
manifest(s)</a>.</p>
        <ul>
<li>If you close this pull request, Updatecli will automatically reopen
it, the next time it runs.</li>
<li>If you close this pull request and delete the base branch, Updatecli
will automatically recreate it, erasing all previous commits made.</li>
        </ul>
        <p>
Feel free to report any issues at <a
href="https://github.com/updatecli/updatecli/issues">github.com/updatecli/updatecli</a>.<br
/>
If you find this tool useful, do not hesitate to star <a
href="https://github.com/updatecli/updatecli/stargazers">our GitHub
repository</a> as a sign of appreciation, and/or to tell us directly on
our <a
href="https://matrix.to/#/#Updatecli_community:gitter.im">chat</a>!
        </p>
      </details>
    </td>
  </tr>
</table>

Co-authored-by: Jenkins Infra Bot (updatecli) <60776566+jenkins-infra-bot@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants