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

feat: CRI support configure https registry #290

Merged
merged 5 commits into from
Oct 24, 2022

Conversation

lyp256
Copy link
Contributor

@lyp256 lyp256 commented Oct 21, 2022

Signed-off-by: lyp256 lyp256@qq.com

What type of PR is this?

/kind feature

What this PR does / why we need it:

Which issue(s) this PR fixes:

Fixes #287

Special notes for reviewers:

Does this PR introduced a user-facing change?

Ability to configure a self-signed certificate registry for an existing cluster

Additional documentation, usage docs, etc.:


@kubeclipper-bot kubeclipper-bot added kind/feature Categorizes issue or PR as related to a new feature. release-note dco-signoff: yes size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. labels Oct 21, 2022
@lyp256 lyp256 changed the title feat: CRI support configure https registry for #287 feat: CRI support configure https registry for #287 (WIP) Oct 21, 2022
@codecov-commenter
Copy link

codecov-commenter commented Oct 21, 2022

Codecov Report

Merging #290 (f71e37f) into master (7185a4e) will decrease coverage by 0.25%.
The diff coverage is 3.23%.

Impacted file tree graph

@@            Coverage Diff             @@
##           master     #290      +/-   ##
==========================================
- Coverage   13.23%   12.98%   -0.26%     
==========================================
  Files          98       99       +1     
  Lines       15214    15522     +308     
==========================================
+ Hits         2014     2015       +1     
- Misses      12960    13265     +305     
- Partials      240      242       +2     
Impacted Files Coverage Δ
pkg/apis/core/v1/handler.go 0.31% <0.00%> (-0.02%) ⬇️
pkg/apis/core/v1/registry.go 0.00% <0.00%> (ø)
pkg/scheme/core/v1/cri/docker.go 0.00% <0.00%> (ø)
pkg/scheme/core/v1/k8s/utils.go 0.00% <ø> (ø)
pkg/scheme/core/v1/k8s/utils_unix.go 0.00% <0.00%> (ø)
pkg/scheme/core/v1/cri/containerd.go 11.37% <5.88%> (-4.56%) ⬇️
pkg/scheme/core/v1/cri/cri.go 52.94% <57.14%> (+32.94%) ⬆️

@x893675
Copy link
Collaborator

x893675 commented Oct 21, 2022

/cc @lixd

@@ -38,7 +39,7 @@ type Cluster struct {
// move offline to metadata annotation
// Offline bool `json:"offline" optional:"true"`
LocalRegistry string `json:"localRegistry,omitempty" optional:"true"`
Masters WorkerNodeList `json:"masters"`
Masters WorkerNodeList `json:"massters"`
Copy link
Collaborator

Choose a reason for hiding this comment

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

typo error

"time"

"github.com/docker/docker/daemon/config"
Copy link
Collaborator

@x893675 x893675 Oct 21, 2022

Choose a reason for hiding this comment

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

seems build error
QQ20221021-150205

Copy link
Collaborator

Choose a reason for hiding this comment

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

use map[string]interface unmarshall docker config, add update value of map[insecure-registryies]

Signed-off-by: lyp256 <lyp256@qq.com>
Signed-off-by: lyp256 <lyp256@qq.com>
Signed-off-by: lyp256 <lyp256@qq.com>
Signed-off-by: lyp256 <lyp256@qq.com>
@x893675 x893675 changed the title feat: CRI support configure https registry for #287 (WIP) feat: CRI support configure https registry Oct 24, 2022
@x893675
Copy link
Collaborator

x893675 commented Oct 24, 2022

/lgtm
/approve

@kubeclipper-bot kubeclipper-bot added the lgtm Indicates that a PR is ready to be merged. label Oct 24, 2022
@kubeclipper-bot
Copy link
Collaborator

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: lyp256, x893675

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

@kubeclipper-bot kubeclipper-bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Oct 24, 2022
@kubeclipper-bot
Copy link
Collaborator

LGTM label has been added.

Git tree hash: 788ee30a5deae9079ed2dc07cd46ed27114d366d

@kubeclipper-bot kubeclipper-bot merged commit 3929d70 into kubeclipper:master Oct 24, 2022
@lyp256 lyp256 deleted the registry branch October 26, 2022 01:35
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. dco-signoff: yes kind/feature Categorizes issue or PR as related to a new feature. lgtm Indicates that a PR is ready to be merged. release-note size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

CRI support for configuration self signed certificate registry
4 participants