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

Propagate ClusterConfiguration in kind correctly #3265

Merged

Conversation

creydr
Copy link
Contributor

@creydr creydr commented Aug 3, 2023

During knative/eventing#7140 I saw, that the ClusterConfiguration is not used correctly (e.g. the cluster domain not set correctly). This is due to an old apiVersion field, which (according to kubernetes-sigs/kind#1466 (comment)) can be dropped.
Also the metadata.name field can be dropped (kind docu: kubeadm-config-patches).
With this fix, configs, like the CLUSTER_SUFFIX will be propagated correctly to kubeadm again.

@knative-prow knative-prow bot added the size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. label Aug 3, 2023
@knative-prow knative-prow bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Aug 3, 2023
@codecov
Copy link

codecov bot commented Aug 3, 2023

Codecov Report

Merging #3265 (b09f8a3) into main (ed50d26) will increase coverage by 0.01%.
Report is 12 commits behind head on main.
The diff coverage is n/a.

@@             Coverage Diff              @@
##               main    #3265      +/-   ##
============================================
+ Coverage     61.87%   61.89%   +0.01%     
- Complexity      764      765       +1     
============================================
  Files           181      181              
  Lines         12200    12200              
  Branches        268      268              
============================================
+ Hits           7549     7551       +2     
+ Misses         4062     4061       -1     
+ Partials        589      588       -1     
Flag Coverage Δ
java-unittests 72.02% <ø> (+0.06%) ⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

see 1 file with indirect coverage changes

@creydr
Copy link
Contributor Author

creydr commented Aug 3, 2023

/assign @matzew @pierDipi

@creydr
Copy link
Contributor Author

creydr commented Aug 8, 2023

@aliok could you PTAL at this PR?

Copy link
Contributor

@matzew matzew left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm
/approve

@matzew matzew added the lgtm Indicates that a PR is ready to be merged. label Aug 15, 2023
@knative-prow
Copy link

knative-prow bot commented Aug 15, 2023

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: creydr, matzew

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@creydr
Copy link
Contributor Author

creydr commented Aug 15, 2023

/retest

@knative-prow knative-prow bot merged commit 60d3d6d into knative-extensions:main Aug 15, 2023
16 of 18 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants