-
Notifications
You must be signed in to change notification settings - Fork 340
added resource details in deprecation message #13060
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
base: master
Are you sure you want to change the base?
Conversation
Reviewer Checklist🔍 Each of these sections need to be checked by the reviewer of the PR 🔍:
|
Signed-off-by: gnana997 <gnana097@gmail.com>
## Motivation **We only need `mesh` resource revert.** Seems that syncing is broken: ``` type: Mesh name: default mtls: enabledBackend: ca-1 backends: - name: ca-1 type: builtin dpCert: rotation: expiration: 1d networking: outbound: passthrough: false routing: localityAwareLoadBalancing: true zoneEgress: true ``` becomes: ``` spec: mtls: backends: - dpCert: rotation: expiration: 1d name: ca-1 type: builtin enabledBackend: ca-1 networking: outbound: passthrough: false routing: {} ``` on the zone ## Implementation information revert Mesh part of kumahq#12895 --------- Signed-off-by: slonka <slonka@users.noreply.github.com> Signed-off-by: gnana997 <gnana097@gmail.com>
## Motivation Adding notes for debugging E2E in IDE ## Implementation information <!-- Explain how this was done and potentially alternatives considered and discarded --> ## Supporting documentation <!-- Is there a MADR? An Issue? A related PR? --> Fix #XX > Changelog: skip <!-- Uncomment the above section to explicitly set a [`> Changelog:` entry here](https://github.com/kumahq/kuma/blob/master/CONTRIBUTING.md#submitting-a-patch)? --> Signed-off-by: Jay Chen <1180092+jijiechen@users.noreply.github.com> Signed-off-by: gnana997 <gnana097@gmail.com>
…mahq#12986) ## Motivation add internal address config onto HttpConnectionManager, more details are available in issue kumahq#12190 ## Implementation information introducing a new configuration item `ipam.knownInternalCIDRs` on zonal CP to allow users specify their known internal address pool and we assign these values when generating Envoy config for HttpConnectionManager ## Supporting documentation <!-- Is there a MADR? An Issue? A related PR? --> fixes kumahq#12190 <!-- > Changelog: skip --> <!-- Uncomment the above section to explicitly set a [`> Changelog:` entry here](https://github.com/kumahq/kuma/blob/master/CONTRIBUTING.md#submitting-a-patch)? --> --------- Signed-off-by: Jay Chen <1180092+jijiechen@users.noreply.github.com> Signed-off-by: gnana997 <gnana097@gmail.com>
## Motivation Minor improvements in `UPGRADE.md` ## Implementation information change wording inline > Changelog: skip <!-- Uncomment the above section to explicitly set a [`> Changelog:` entry here](https://github.com/kumahq/kuma/blob/master/CONTRIBUTING.md#submitting-a-patch)? --> --------- Signed-off-by: Jay Chen <1180092+jijiechen@users.noreply.github.com> Signed-off-by: Jay Jijie Chen <1180092+jijiechen@users.noreply.github.com> Co-authored-by: Lukasz Dziedziak <lukidzi@gmail.com> Co-authored-by: Icarus Wu <icaruswu66@qq.com> Signed-off-by: gnana997 <gnana097@gmail.com>
3e1792b
to
04e1e7b
Compare
…ation-reource-details
Signed-off-by: gnana997 <gnana097@gmail.com>
…a997/kuma into deprecation-reource-details
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
The CI ran over time |
@gnana997 Could you fix the unit test? |
Hi @lahabana , I tried the tests and all of them passed however it has updated json and yaml files with warnings of deprecated resources. |
@gnana997 after new golden files were generated via |
Signed-off-by: gnana997 <gnana097@gmail.com>
3a30e02
to
0a75162
Compare
Oh ok. Got it. I have pushed the changes. |
pkg/api-server/testdata/resources/crud/put_meshaccesslog_00.golden.json
Outdated
Show resolved
Hide resolved
It's a little odd to return the resource name in the deprecation message. What are we trying to achieve here? Readability in kumactl apply? If that's the case adding the resource type and name in the response should be done in kumactl not in the response of the api |
1 similar comment
It's a little odd to return the resource name in the deprecation message. What are we trying to achieve here? Readability in kumactl apply? If that's the case adding the resource type and name in the response should be done in kumactl not in the response of the api |
Because I noticed that the
|
Signed-off-by: gnana997 <gnana097@gmail.com>
{ | ||
"warnings": [ | ||
"MeshAccessLog type resource \"my-access-log\" has the following deprecated fields: " | ||
] | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@gnana997 Hi, you can see there are no deprecation details in this sentence as I said before. It's an obvious unexpected output, and we need to figure out why. I'll have a look at it later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@gnana997 Please apply my new changes, then update the golden files again.
Co-authored-by: Icarus Wu <icaruswu66@qq.com> Signed-off-by: Gnana Siva Sai V <gnana097@gmail.com>
The I believe that the problem is in the log message not in the deprecation warning message. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We need to get background on why KubeAPIWarningLogger doesn't add context. Maybe there's a workaround that's nicer. Worth looking at how other projects to deprecations
Motivation
#13030 : Helps user debugging in the usage of deprecated resources
Implementation information
Added resource name and resource meta information along with the deprecation resource errors
Supporting documentation
Fix #13030