Open
Conversation
3e51f58 to
4841a81
Compare
4841a81 to
9af1a7c
Compare
9af1a7c to
d03cb6a
Compare
d03cb6a to
860bd78
Compare
860bd78 to
26b279b
Compare
26b279b to
83bbcaf
Compare
12bd6f0 to
92e8f14
Compare
92e8f14 to
7f4db9c
Compare
7f4db9c to
3bad17c
Compare
3bad17c to
275c732
Compare
72e508e to
54c2692
Compare
10f1082 to
73fcfe0
Compare
bca7301 to
dec6e93
Compare
dec6e93 to
42d3e45
Compare
42d3e45 to
57bd3e0
Compare
3ad0234 to
d72bb99
Compare
d72bb99 to
8ab48b1
Compare
8ab48b1 to
d2bb667
Compare
d2bb667 to
e530b7a
Compare
e530b7a to
2a185c3
Compare
2ff70e4 to
95365df
Compare
95365df to
8e366c6
Compare
9f5c692 to
7883146
Compare
7883146 to
d70aa02
Compare
d70aa02 to
fded3c7
Compare
cb65340 to
531ecb6
Compare
51082cb to
d5edf2e
Compare
d5edf2e to
a18aec3
Compare
1b7c047 to
54dbb0f
Compare
54dbb0f to
081ceaa
Compare
081ceaa to
510941a
Compare
510941a to
eb97254
Compare
eb97254 to
db60a91
Compare
db60a91 to
8a2c9e7
Compare
8a2c9e7 to
d4d7726
Compare
d4d7726 to
ee41fc5
Compare
ee41fc5 to
38cc10c
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
3.23.1→4.28.0Release Notes
pulumi/pulumi-kubernetes (Pulumi.Kubernetes)
v4.28.0Changed
v4.27.0Fixed
Added
Chart v4andRelease v3will now login to private OCIregistries as expected.
(#2911 and #1914)
v4.26.0Fixed
#4122 Implements a new provider config option,
alwaysRender, which setsDiff_Someto true when used in combination withrenderYAMLtoDirectory.This allows for user-defined opt-in behavior for YAML manifests to be idempotently generated on every
pulumi up, and for Update() to show these changes to a user.Fixed a race condition in StatefulSet await logic where Pulumi could
incorrectly report a rollout as complete before the controller had processed
the update. This occurred when Pulumi checked status fields before the
controller updated
observedGeneration, causing stale "ready" values to betrusted.
Fixed a regression of
#2943 which could
cause Deployments to erroneously report diffs.
Changed
Upgraded
helm.sh/helmto v3.18.6. (#3969)#4156 Upgrade Kubernetes schema and libraries to v1.35.1
v4.25.0v4.24.1Fixed
Changed
helm.sh/helmto v3.18.6. (#3969)v4.24.0Added
plainHttpoption to thev4.Chartresource. (#3250)Changed
The
pulumi.com/waitForannotation now uses anRFC9535-compliant JSONPath
parser. This makes it possible to wait for more complex scenarios.
For example:
To wait for a Pod's
status.phaseto be "Running" or "Succeeded":pulumi.com/waitFor: "jsonpath={.status[?@​ == 'Running' || @​ == 'Succeeded' ]}"To wait for for an object to have a "Failed" or "Complete" condition with
a "True" value:
pulumi.com/waitFor: "jsonpath={.conditions[?(@​.type=='Failed'||@​.type=='Complete')].status}=True(Tools like jsonpath.com are very helpful for
ensuring your JSONPath expression works as expected.)
Importantly, please note that
kubectl wait --for=jsonpath=...supports onlya subset of RFC9535. This means some complex
waitForannotations will notbe reproducible with
kubectl.Existing expressions should continue to work normally with one notable
exception: a selector like
.items[]now requires an explicit wildcard, i.e..items[*].As a reminder, the
pulumi.com/waitForannotation is experimental andsubject to change. Similarly, RFC9535 is still only proposed and may also
change in the future.
enableConfigMapMutableandenableSecretMutableare now stable.(#3886)
Fixed
Helm resources all now use the correct
registry/config.jsonfile forcredentials. For backward-compatibility
registry.jsonis preferred ifit exists. (#3606)
Fixed an issue where deletions could take longer than necessary. (#3317)
Significantly reduced memory usage. (#3713)
Fixed incorrect deprecation warnings for VolumeAttributesClass. (#3772)
SecretPatch inputs are now automatically marked as secret.
v4.23.0Changed
v4.22.2Fixed
valueYamlFilesfield inhelm.v3.Releaseresources are nil (#3601)v4.22.1Fixed
v4.22.0Changed
Fixed
v4.21.1Added
v4.21.0Changed
pulumi-javato versionv1.0.0(#3436)v4.20.0Added
(#3363)
v4.19.0Changed
v4.18.4Changed
punycodedeprecation warnings by using nativefetchinstead ofnode-fetch.(#3301)
Fixed
pulumi.com/waitForand other await annotations now correctly take precedence over default await logic.(#3329)
JSONPath expressions used with the
pulumi.com/waitForannotation will no longer hang indefinitely if they match non-primitive fields.(#3345)
[java] CRDs that contain any
x-kubernetes-*fields can now be succesfully created and managed by Pulumi.(#3325)
v4.18.3Fixed
Objects created on clusters older than 1.18 will no longer see a
before-first-applyconflict when Pulumi performs a server-side apply forthe first time. (#3275)
The provider's user agent is now set correctly when communicating with
the Kubernetes API server.
(#3267)
v4.18.2Fixed
potential "pulumi.runtime.invokeOutput is not a function" errors.
(pulumi/pulumi#17518)
v4.18.1Added
Changed
v4.18.0Added
The new
enableSecretMutableprovider configuration option treats changes toSecretsas updates instead of replacements (similar to theenableConfigMapMutableoption).The default replacement behavior can be preserved for a particular
Secretby setting its
immutablefield totrue.(#2291)
Note: These options (
enableSecretMutableandenableConfigMapMutable)may become the default behavior in a future v5 release of the provider.
Programs that depend on the replacement of
SecretsandConfigMaps(e.g.to trigger updates for downstream dependencies like
Deployments) arerecommended to explicitly specify
immutable: true.A warning is now emitted if an object has finalizers which might be blocking
deletion. (#1418)
EXPERIMENTAL: Generic await logic is now available as an opt-in feature.
Running a program with
PULUMI_K8S_AWAIT_ALL=truewill now cause Pulumi toawait readiness for all resources, including custom resources.
Generic readiness is determined according to some well-known conventions (like
the "Ready" condition) as determined by cli-utils.
Pulumi's current behavior, without this feature enabled, is to assume some
resources are immediately available, which can cause downstream resources to
fail.
Existing readiness logic is unaffected by this setting.
(#2996)
EXPERIMENTAL: The
pulumi.com/waitForannotation was introduced to allowfor custom readiness checks. This override Pulumi's own await logic for the
resource (however the
pulumi.com/skipAwaitannotation still takesprecedence).
The value of this annotation can take 3 forms:
A string prefixed with
jsonpath=followed by aJSONPath
expression and an optional value.
The JSONPath expression accepts the same syntax as
kubectl get -o jsonpath={...}.If a value is provided, the resource is considered ready when the
JSONPath expression evaluates to the same value. For example this
resource expects its "phase" field to have a value of "Running":
If a value is not provided, the resource will be considered ready when
any value exists at the given path, similar to
kubectl wait --for jsonpath=.... This resource will wait until it has a webhook configuredwith a CA bundle:
A string prefixed with
condition=followed by the type of thecondition and an optional status. This matches the behavior of
kubectl wait --for=condition=...and will wait until the resource has amatching condition. The expected status defaults to "True" if not
specified.
A string containing a JSON array of multiple
jsonpath=andcondition=expressions.Pulumi will now emit logs for any Kubernetes "Warning" Events associated with
resources being created, updated or deleted.
(https://redirect.github.com/pulumi/pulumi-kubernetes/pull/3135/files)
Fixed
The
immutablefield is now respected forConfigMapswhen the provider is configured withenableConfigMapMutable.(#3181)
Fixed a panic that could occur during deletion. (#3157)
v4.17.1Fixed
ServiceAccounts. (#3166)clusterIdentifierprovider configuration. (#3168)v4.17.0Changed
Fixed
Serviceswith selectors targeting 0Podswill no longer hang indefinitely.(#605)
Serviceswithout selectors will no longer hang indefinitely.(#799)
v4.16.0Added
clusterIdentifierconfiguration can now be used to manually control thereplacement behavior of a provider resource.
(#3068)
Pod errors now include the pod's last termination state, as well as the pod's
termination message if available.
(#3091)
The pod's termination message can be helpful in
CrashLoopBackOffsituations butwill only be reported if it was correctly configured.
By default, the pod's termination message is read from
/dev/termination-log. This location can be configured withterminationMessagePath.Use
terminationMessagePolicy: FallbackToLogsOnErrorto use the pod's logsas its termination message.
Documentation is now generated for all languages supported by overlay types.
(#3107)
Fixed
CustomResourceoverlays. (#3120)affected resource. (#3128)
PersistentVolumeClaimswith a bind mode ofWaitForFirstConsumerwill nolonger hang indefinitely. (#3130)
v4.15.0Changed
CustomResourceshould have plainapiVersionandkindproperties (#3079)(#3144)
Fixed
v4.14.0Added
TypedDictinput types for the Python SDK (#3070)Changed
Releaseresource no longer ignores empty lists when merging values. (#2995)Fixed
Chartv4 now handles an array of assets. (#3061)v4.13.1Added
Changed
Fixed
replaceUnreadyannotations and an unreachable cluster connection. (#3024)v4.12.0Added
Changed
valueYamlFilesnow more closely matches Helm's behavior. (#2963)Fixed
null. (#1970)v4.11.0v4.10.0New Features
A new MLC-based implementation of
ConfigGroupand ofConfigFileis now available in the "yaml/v2" package. These resources areusable in all Pulumi languages, including Pulumi YAML and in the Java Pulumi SDK.
Note that transformations aren't supported in this release (see pulumi/pulumi#12996).
v4.9.1helm,kustomize, andyamlcomponents (#2863)v4.9.0v4.8.1v4.8.0v4.7.1v4.7.0Breaking Changes
In previous versions of the pulumi-kubernetes .NET SDK, the
ConfigFileandConfigGroupcomponent resources inadvertently assigned the wrong parent to the child resource(s).This would happen when the component resource itself had a parent; the child would be assigned that same parent. This also had the effect of disregarding the component resource's provider in favor of the parent's provider.
For example, here's a before/after look at the component hierarchy:
Before:
After:
This release addresses this issue and attempts to heal existing stacks using aliases. This is effective at avoiding a replacement except in the case where the child was created with the wrong provider. In this case, Pulumi will suggest a replacement of the child resource(s), such that they use the correct provider.
v4.6.1v4.6.0PULUMI_KUBERNETES_MANAGED_BY_LABELenv var with SSA created objects (#2711)Resources Renamed
#/types/kubernetes:core/v1:ResourceRequirements#/types/kubernetes:core/v1:VolumeResourceRequirements#/types/kubernetes:core/v1:ResourceRequirementsPatch#/types/kubernetes:core/v1:VolumeResourceRequirementsPatchNew Resources
flowcontrol.apiserver.k8s.io/v1.FlowSchemaflowcontrol.apiserver.k8s.io/v1.FlowSchemaListflowcontrol.apiserver.k8s.io/v1.FlowSchemaPatchflowcontrol.apiserver.k8s.io/v1.PriorityLevelConfigurationflowcontrol.apiserver.k8s.io/v1.PriorityLevelConfigurationListflowcontrol.apiserver.k8s.io/v1.PriorityLevelConfigurationPatchnetworking.k8s.io/v1alpha1.ServiceCIDRnetworking.k8s.io/v1alpha1.ServiceCIDRListnetworking.k8s.io/v1alpha1.ServiceCIDRPatchstorage.k8s.io/v1alpha1.VolumeAttributesClassstorage.k8s.io/v1alpha1.VolumeAttributesClassListstorage.k8s.io/v1alpha1.VolumeAttributesClassPatchv4.5.6v4.5.5v4.5.4v4.5.3v4.5.2v4.5.1v4.5.0v4.4.0v4.3.0v4.2.0source-based and wheel distributions are now published. For most users the installs will now favor
the wheel distribution, but users invoking pip with
--no-binary :all:will continue havinginstalls based on the source distribution.
v4.1.1(see #2540)
v4.1.0v4.0.3v4.0.2v4.0.1v4.0.0Breaking changes:
Other changes:
v3.30.2v3.30.1v3.30.0v3.29.1v3.29.0v3.28.1v3.28.0SelfSubjectReview, SelfSubjectAccessReview, SelfSubjectRulesReview, and SubjectAccessReview (#2413)
v3.27.1v3.27.0v3.26.0v3.25.0New resources
Resources moved from v1alpha1 to v1alpha2
Resources moved from v1beta1 to v1
Resources renamed
New Features
v3.24.3v3.24.2v3.24.1invoke_yaml_decodeinto ConfigGroup for python (#2317)v3.24.0outputsafterSecret.get(#2300)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 is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.