profile
viewpoint

lovebaby979/community 0

Kubernetes community content

lovebaby979/documentation 0

Kata Containers version 1.x documentation (for version 2.x see https://github.com/kata-containers/kata-containers).

lovebaby979/metrics-server 0

Cluster-wide aggregator of resource usage data.

lovebaby979/rabbitmq-server 0

Open source multi-protocol messaging broker

lovebaby979/rabbitmq-tutorials 0

Tutorials for using RabbitMQ in various ways

issue closedcontainers/podman

how to login my repository

/kind feature

Description podman login my repository report error,how to setting?

error: podman login registry.my.com:31231 Authenticating with existing credentials... Existing credentials are invalid, please enter valid username and password Username (admin): admin Password: Error: error authenticating creds for "registry.my.com:31231": pinging docker registry returned: Get https://registry.my.com:31231/v2/: http: server gave HTTP response to HTTPS client

closed time in 4 days

lovebaby979

issue commentcontainers/podman

how to login my repository

@Luap99 Thank you!

lovebaby979

comment created time in 4 days

issue openedcontainers/podman

how to login my repository

/kind feature

Description podman login my repository report error,how to setting?

error: podman login registry.my.com:31231 Authenticating with existing credentials... Existing credentials are invalid, please enter valid username and password Username (admin): admin Password: Error: error authenticating creds for "registry.my.com:31231": pinging docker registry returned: Get https://registry.my.com:31231/v2/: http: server gave HTTP response to HTTPS client

created time in 8 days

issue commentkubernetes-sigs/cri-tools

how to login my repository

sorry,how to remove@saschagrunert

lovebaby979

comment created time in 8 days

issue openedkubernetes-sigs/cri-tools

how to login my repository

podman login my repository report error,how to setting?

error:

podman login registry.my.com:31231

Authenticating with existing credentials... Existing credentials are invalid, please enter valid username and password Username (admin): admin Password: Error: error authenticating creds for "registry.my.com:31231": pinging docker registry returned: Get https://registry.my.com:31231/v2/: http: server gave HTTP response to HTTPS client

created time in 9 days

fork lovebaby979/documentation

Kata Containers version 1.x documentation (for version 2.x see https://github.com/kata-containers/kata-containers).

https://katacontainers.io/

fork in 11 days

issue closedkata-containers/runtime

how to cross build binary for arm64 on amd64 platform

Description of problem

how to build binary for arm64 on amd64 platform

build binary for arm64 on amd64(ubuntu18.04) I update variable “golang_version_raw” in golang.mk, replace “amd64” to “arm64”, when make, report the errors:

(cd cli && GOARCH=arm64 go build -buildmode=pie -o /usr/local/gopath/src/github.com/kata-containers/runtime/kata-runtime .)

github.com/kata-containers/runtime/cli

./kata-check_arm64.go:32:44: undefined: kernelModule ./kata-check_arm64.go:53:44: undefined: kvmExtension ./kata-check_arm64.go:67:9: undefined: genericKvmIsUsable ./kata-check_arm64.go:71:18: undefined: genericCheckKVMExtensions ./kata-check_arm64.go:98:39: undefined: vmContainerCapableDetails ./kata-check_arm64.go:100:12: undefined: getCPUInfo ./kata-check_arm64.go:105:16: undefined: checkKernelModules ./kata-check_arm64.go:114:33: undefined: failMessage ./main.go:140:2: undefined: kataCheckCLICommand ./main.go:143:2: undefined: kataOverheadCLICommand ./kata-check_arm64.go:114:33: too many errors Makefile:566: recipe for target '/usr/local/gopath/src/github.com/kata-containers/runtime/kata-runtime' failed make: *** [/usr/local/gopath/src/github.com/kata-containers/runtime/kata-runtime] Error 2

closed time in a month

lovebaby979

issue openedkata-containers/runtime

how to build binary for arm64 on amd64 platform

Description of problem

how to build binary for arm64 on amd64 platform

build binary for arm64 on amd64(ubuntu18.04) I update variable “golang_version_raw” in golang.mk, replace “amd64” to “arm64”, when make, report the errors:

created time in a month

issue commentcri-o/cri-o

pod status is ready, logs report error

@haircommander thank you!

lovebaby979

comment created time in a month

issue commentcri-o/cri-o

pod status is ready, logs report error

@haircommander thank you. Problem not resolve.

lovebaby979

comment created time in a month

issue openedcri-o/cri-o

pod status is ready, logs report error

ubuntu: 18.04 crio: 1.18.3 runtime: kata-runtime 1.11.3 K8S: 1.14.3

root@mgt03:~# crictl pods coredns POD ID CREATED STATE NAME NAMESPACE ATT 558ac990df54e 20 minutes ago Ready coredns-d5rz8 kube-system 1

root@mgt03:~# crictl logs 558ac990df54e E0915 09:18:06.277998 62846 remote_runtime.go:295] ContainerStatus "558ac990df54e" from runtime service failed: rpc error: code = NotFound desc = could not find container "558ac990df54e": specified container not found: 558ac990df54e26dba04ccb2ce7cbd091a739878a8075ebbed12cfedb033dac0 FATA[0000] rpc error: code = NotFound desc = could not find container "558ac990df54e": specified container not found: 558ac990df54e26dba04ccb2ce7cbd091a739878a8075ebbed12cfedb033dac0

root@mgt03:~# crictl logs 558ac990df54e E0915 09:18:06.277998 62846 remote_runtime.go:295] ContainerStatus "558ac990df54e" from runtime service failed: rpc error: code = NotFound desc = could not find container "558ac990df54e": specified container not found: 558ac990df54e26dba04ccb2ce7cbd091a739878a8075ebbed12cfedb033dac0 FATA[0000] rpc error: code = NotFound desc = could not find container "558ac990df54e": specified container not found: 558ac990df54e26dba04ccb2ce7cbd091a739878a8075ebbed12cfedb033dac0


how to resolve the problem?

created time in a month

create barnchlovebaby979/cri-o

branch : update-podman

created branch time in a month

create barnchlovebaby979/cri-o

branch : podman

created branch time in a month

create barnchlovebaby979/cri-o

branch : using2

created branch time in a month

issue closedalpinelinux/docker-alpine

where could get image for loogson(mips64)?

where could get image for loogson(mips64)? I want to build image run on loogson linux,but I couldn't find the release for loogson(mips64) linux.

closed time in a month

lovebaby979

issue closedkubernetes-sigs/controller-runtime

client delete job,but pod not delete

delete job created by ctx, but pod created by job was not deleted. delete job code: getJob := &batchv1.Job{} myErr := r.Get(ctx, types.NamespacedName{Namespace: "csf", Name: jobName}, getJob) if myErr != nil && !api_errors.IsNotFound(myErr) { r.Log.WithValues("Reconcile CsfTemplate get job fail!") return false, myErr } else if api_errors.IsNotFound(myErr) { return true, nil } errDel := r.Delete(ctx, getJob) if errDel != nil { r.Log.Error(errDel, " deleteJob fail! Namespace["+"csf"+"],JobName["+jobName+"]\n", errDel.Error()) }else{ r.Log.Info(" deleteJob success! Namespace["+"csf"+"],JobName["+jobName+"]\n") }

closed time in a month

lovebaby979

fork lovebaby979/cri-o

Open Container Initiative-based implementation of Kubernetes Container Runtime Interface

https://cri-o.io

fork in a month

pull request commentcri-o/cri-o

update link for podman

@sboeuf

lovebaby979

comment created time in a month

PR closed cri-o/cri-o

Reviewers
update link for podman dco-signoff: no needs-ok-to-test release-note

<!-- Thanks for sending a pull request!

Please be aware that we're following the Kubernetes guidelines of contributing to this project. This means that we have to use this mandatory template for all of our pull requests.

Please also make sure you've read and understood our contributing guidelines (https://github.com/cri-o/cri-o/blob/master/CONTRIBUTING.md) as well as ensuring that all your commits are signed with git commit -s.

Here are some additional tips for you:

  • If this is your first time, please read our contributor guidelines: https://git.k8s.io/community/contributors/guide#your-first-contribution and developer guide https://git.k8s.io/community/contributors/devel/development.md#development-guide
  • Please label this pull request according to what type of issue you are addressing, especially if this is a release targeted pull request. For reference on required PR/issue labels, read here: https://git.k8s.io/community/contributors/devel/sig-release/release.md#issuepr-kind-label
  • If you want faster PR reviews, read how: https://git.k8s.io/community/contributors/guide/pull-requests.md#best-practices-for-faster-reviews
  • If the PR is unfinished, see how to mark it: https://git.k8s.io/community/contributors/guide/pull-requests.md#marking-unfinished-pull-requests -->

What type of PR is this?

documentation

What this PR does / why we need it:

update link for pod man

Which issue(s) this PR fixes:

None

Special notes for your reviewer:

Does this PR introduce a user-facing change?

none

update broken link for podman
+25 -25

5 comments

1 changed file

lovebaby979

pr closed time in 2 months

PR closed cri-o/cri-o

Reviewers
broken link approved dco-signoff: no lgtm ok-to-test release-note

<!-- Thanks for sending a pull request!

Please be aware that we're following the Kubernetes guidelines of contributing to this project. This means that we have to use this mandatory template for all of our pull requests.

Please also make sure you've read and understood our contributing guidelines (https://github.com/cri-o/cri-o/blob/master/CONTRIBUTING.md) as well as ensuring that all your commits are signed with git commit -s.

Here are some additional tips for you:

  • If this is your first time, please read our contributor guidelines: https://git.k8s.io/community/contributors/guide#your-first-contribution and developer guide https://git.k8s.io/community/contributors/devel/development.md#development-guide
  • Please label this pull request according to what type of issue you are addressing, especially if this is a release targeted pull request. For reference on required PR/issue labels, read here: https://git.k8s.io/community/contributors/devel/sig-release/release.md#issuepr-kind-label
  • If you want faster PR reviews, read how: https://git.k8s.io/community/contributors/guide/pull-requests.md#best-practices-for-faster-reviews
  • If the PR is unfinished, see how to mark it: https://git.k8s.io/community/contributors/guide/pull-requests.md#marking-unfinished-pull-requests -->

What type of PR is this?

<!-- Uncomment only one /kind <> line, hit enter to put that in a new line, and remove leading whitespace from that line: -->

kind documentation

What this PR does / why we need it:

update wrong path to tutorials

Which issue(s) this PR fixes:

<!-- Automatically closes linked issue when PR is merged. Usage: Fixes #<issue number>, or Fixes (paste link of issue). --> None

Special notes for your reviewer:

Does this PR introduce a user-facing change?

None

update broken link to files in tutorial
+3 -3

9 comments

1 changed file

lovebaby979

pr closed time in 2 months

PR closed cri-o/cri-o

Reviewers
update link to tutorials/crictl dco-signoff: no do-not-merge/release-note-label-needed kind/bug needs-ok-to-test

<!-- Thanks for sending a pull request!

Please be aware that we're following the Kubernetes guidelines of contributing to this project. This means that we have to use this mandatory template for all of our pull requests.

Please also make sure you've read and understood our contributing guidelines (https://github.com/cri-o/cri-o/blob/master/CONTRIBUTING.md) as well as ensuring that all your commits are signed with git commit -s.

Here are some additional tips for you:

  • If this is your first time, please read our contributor guidelines: https://git.k8s.io/community/contributors/guide#your-first-contribution and developer guide https://git.k8s.io/community/contributors/devel/development.md#development-guide
  • Please label this pull request according to what type of issue you are addressing, especially if this is a release targeted pull request. For reference on required PR/issue labels, read here: https://git.k8s.io/community/contributors/devel/sig-release/release.md#issuepr-kind-label
  • If you want faster PR reviews, read how: https://git.k8s.io/community/contributors/guide/pull-requests.md#best-practices-for-faster-reviews
  • If the PR is unfinished, see how to mark it: https://git.k8s.io/community/contributors/guide/pull-requests.md#marking-unfinished-pull-requests -->

What type of PR is this?

<!-- Uncomment only one /kind <> line, hit enter to put that in a new line, and remove leading whitespace from that line: -->

/kind api-change /kind bug /kind cleanup /kind dependency-change /kind deprecation /kind design /kind documentation /kind failing-test /kind feature /kind flake

What this PR does / why we need it:

Which issue(s) this PR fixes:

<!-- Automatically closes linked issue when PR is merged. Usage: Fixes #<issue number>, or Fixes (paste link of issue). -->

<!-- Fixes # or None -->

Special notes for your reviewer:

Does this PR introduce a user-facing change?

<!-- If no, just write None in the release-note block below. If yes, a release note is required: Enter your extended release note in the block below. If the PR requires additional action from users switching to the new release, include the string "action required".

For more information on release notes see: https://git.k8s.io/community/contributors/guide/release-notes.md -->


+1 -1

8 comments

1 changed file

lovebaby979

pr closed time in 2 months

pull request commentcri-o/cri-o

broken link

@nalind

lovebaby979

comment created time in 2 months

PR opened cri-o/cri-o

Reviewers
broken link

Signed-off-by: wangjibao.lc wangjibao.lc@inspur.com

<!-- Thanks for sending a pull request!

Please be aware that we're following the Kubernetes guidelines of contributing to this project. This means that we have to use this mandatory template for all of our pull requests.

Please also make sure you've read and understood our contributing guidelines (https://github.com/cri-o/cri-o/blob/master/CONTRIBUTING.md) as well as ensuring that all your commits are signed with git commit -s.

Here are some additional tips for you:

  • If this is your first time, please read our contributor guidelines: https://git.k8s.io/community/contributors/guide#your-first-contribution and developer guide https://git.k8s.io/community/contributors/devel/development.md#development-guide
  • Please label this pull request according to what type of issue you are addressing, especially if this is a release targeted pull request. For reference on required PR/issue labels, read here: https://git.k8s.io/community/contributors/devel/sig-release/release.md#issuepr-kind-label
  • If you want faster PR reviews, read how: https://git.k8s.io/community/contributors/guide/pull-requests.md#best-practices-for-faster-reviews
  • If the PR is unfinished, see how to mark it: https://git.k8s.io/community/contributors/guide/pull-requests.md#marking-unfinished-pull-requests -->

What type of PR is this?

<!-- Uncomment only one /kind <> line, hit enter to put that in a new line, and remove leading whitespace from that line: --> documentation

What this PR does / why we need it:

update broken link for tutorials

Which issue(s) this PR fixes:

None

Special notes for your reviewer:

update broken link for tutorials

Does this PR introduce a user-facing change?

None

update broken link for tutorials
+3 -3

0 comment

1 changed file

pr created time in 2 months

create barnchlovebaby979/cri-o

branch : using2

created branch time in 2 months

PR opened cri-o/cri-o

Reviewers
update link for podman

Signed-off-by: wangjibao.lc wangjibao.lc@inspur.com

<!-- Thanks for sending a pull request!

Please be aware that we're following the Kubernetes guidelines of contributing to this project. This means that we have to use this mandatory template for all of our pull requests.

Please also make sure you've read and understood our contributing guidelines (https://github.com/cri-o/cri-o/blob/master/CONTRIBUTING.md) as well as ensuring that all your commits are signed with git commit -s.

Here are some additional tips for you:

  • If this is your first time, please read our contributor guidelines: https://git.k8s.io/community/contributors/guide#your-first-contribution and developer guide https://git.k8s.io/community/contributors/devel/development.md#development-guide
  • Please label this pull request according to what type of issue you are addressing, especially if this is a release targeted pull request. For reference on required PR/issue labels, read here: https://git.k8s.io/community/contributors/devel/sig-release/release.md#issuepr-kind-label
  • If you want faster PR reviews, read how: https://git.k8s.io/community/contributors/guide/pull-requests.md#best-practices-for-faster-reviews
  • If the PR is unfinished, see how to mark it: https://git.k8s.io/community/contributors/guide/pull-requests.md#marking-unfinished-pull-requests -->

What type of PR is this?

<!-- Uncomment only one /kind <> line, hit enter to put that in a new line, and remove leading whitespace from that line: --> documentation

What this PR does / why we need it:

update broken link for podman

Which issue(s) this PR fixes:

None

Special notes for your reviewer:

Does this PR introduce a user-facing change?

None

update broken link for podman tutorial
+25 -25

0 comment

1 changed file

pr created time in 2 months

create barnchlovebaby979/cri-o

branch : update-podman

created branch time in 2 months

PR opened cri-o/cri-o

Reviewers
update link for podman

<!-- Thanks for sending a pull request!

Please be aware that we're following the Kubernetes guidelines of contributing to this project. This means that we have to use this mandatory template for all of our pull requests.

Please also make sure you've read and understood our contributing guidelines (https://github.com/cri-o/cri-o/blob/master/CONTRIBUTING.md) as well as ensuring that all your commits are signed with git commit -s.

Here are some additional tips for you:

  • If this is your first time, please read our contributor guidelines: https://git.k8s.io/community/contributors/guide#your-first-contribution and developer guide https://git.k8s.io/community/contributors/devel/development.md#development-guide
  • Please label this pull request according to what type of issue you are addressing, especially if this is a release targeted pull request. For reference on required PR/issue labels, read here: https://git.k8s.io/community/contributors/devel/sig-release/release.md#issuepr-kind-label
  • If you want faster PR reviews, read how: https://git.k8s.io/community/contributors/guide/pull-requests.md#best-practices-for-faster-reviews
  • If the PR is unfinished, see how to mark it: https://git.k8s.io/community/contributors/guide/pull-requests.md#marking-unfinished-pull-requests -->

What type of PR is this?

documentation

What this PR does / why we need it:

update link for pod man

Which issue(s) this PR fixes:

None

Special notes for your reviewer:

Does this PR introduce a user-facing change?

none

update broken link for podman
+25 -25

0 comment

1 changed file

pr created time in 2 months

create barnchlovebaby979/cri-o

branch : podman

created branch time in 2 months

pull request commentcri-o/cri-o

broken link

test

lovebaby979

comment created time in 2 months

PR opened cri-o/cri-o

Reviewers
broken link

<!-- Thanks for sending a pull request!

Please be aware that we're following the Kubernetes guidelines of contributing to this project. This means that we have to use this mandatory template for all of our pull requests.

Please also make sure you've read and understood our contributing guidelines (https://github.com/cri-o/cri-o/blob/master/CONTRIBUTING.md) as well as ensuring that all your commits are signed with git commit -s.

Here are some additional tips for you:

  • If this is your first time, please read our contributor guidelines: https://git.k8s.io/community/contributors/guide#your-first-contribution and developer guide https://git.k8s.io/community/contributors/devel/development.md#development-guide
  • Please label this pull request according to what type of issue you are addressing, especially if this is a release targeted pull request. For reference on required PR/issue labels, read here: https://git.k8s.io/community/contributors/devel/sig-release/release.md#issuepr-kind-label
  • If you want faster PR reviews, read how: https://git.k8s.io/community/contributors/guide/pull-requests.md#best-practices-for-faster-reviews
  • If the PR is unfinished, see how to mark it: https://git.k8s.io/community/contributors/guide/pull-requests.md#marking-unfinished-pull-requests -->

What type of PR is this?

<!-- Uncomment only one /kind <> line, hit enter to put that in a new line, and remove leading whitespace from that line: -->

kind documentation

What this PR does / why we need it:

update wrong path to tutorials

Which issue(s) this PR fixes:

<!-- Automatically closes linked issue when PR is merged. Usage: Fixes #<issue number>, or Fixes (paste link of issue). --> None

Special notes for your reviewer:

Does this PR introduce a user-facing change?

None

update broken link to files in tutorial
+3 -3

0 comment

1 changed file

pr created time in 2 months

create barnchlovebaby979/cri-o

branch : using

created branch time in 2 months

pull request commentcri-o/cri-o

update link to tutorials/crictl

What type of PR is this? /kind bug

What this PR does / why we need it: update broken link

lovebaby979

comment created time in 2 months

PR opened cri-o/cri-o

Reviewers
update link to tutorials/crictl

<!-- Thanks for sending a pull request!

Please be aware that we're following the Kubernetes guidelines of contributing to this project. This means that we have to use this mandatory template for all of our pull requests.

Please also make sure you've read and understood our contributing guidelines (https://github.com/cri-o/cri-o/blob/master/CONTRIBUTING.md) as well as ensuring that all your commits are signed with git commit -s.

Here are some additional tips for you:

  • If this is your first time, please read our contributor guidelines: https://git.k8s.io/community/contributors/guide#your-first-contribution and developer guide https://git.k8s.io/community/contributors/devel/development.md#development-guide
  • Please label this pull request according to what type of issue you are addressing, especially if this is a release targeted pull request. For reference on required PR/issue labels, read here: https://git.k8s.io/community/contributors/devel/sig-release/release.md#issuepr-kind-label
  • If you want faster PR reviews, read how: https://git.k8s.io/community/contributors/guide/pull-requests.md#best-practices-for-faster-reviews
  • If the PR is unfinished, see how to mark it: https://git.k8s.io/community/contributors/guide/pull-requests.md#marking-unfinished-pull-requests -->

What type of PR is this?

<!-- Uncomment only one /kind <> line, hit enter to put that in a new line, and remove leading whitespace from that line: -->

/kind api-change /kind bug /kind cleanup /kind dependency-change /kind deprecation /kind design /kind documentation /kind failing-test /kind feature /kind flake

What this PR does / why we need it:

Which issue(s) this PR fixes:

<!-- Automatically closes linked issue when PR is merged. Usage: Fixes #<issue number>, or Fixes (paste link of issue). -->

<!-- Fixes # or None -->

Special notes for your reviewer:

Does this PR introduce a user-facing change?

<!-- If no, just write None in the release-note block below. If yes, a release note is required: Enter your extended release note in the block below. If the PR requires additional action from users switching to the new release, include the string "action required".

For more information on release notes see: https://git.k8s.io/community/contributors/guide/release-notes.md -->


+1 -1

0 comment

1 changed file

pr created time in 2 months

create barnchlovebaby979/cri-o

branch : ctlcli

created branch time in 2 months

push eventlovebaby979/cri-o

Peter Hunt

commit sha 4ed669482cafbacc76f62f58e73644f7f5f6bedc

managed ns: ignore `PID not initialized` on sandbox creation everytime we create a sandbox with a pinned namespace, we spit out an error that says: `Pid for infra container $id not found: PID not initialized` in the pinned namespace case, we create the namespaces, create the networking stack (giving the created net namespace to the plugin), THEN create the pod. Thus, we don't expect the infra container to be initialized. Fix this by ignoring ErrNotInitialized when we're fetching the infraPid when finding the namespaces. We can safely do this because the managed namespace case is covered (we don't use the pid, but use the managed namespace struct we've created) And in the non-managed namespace case, we will (correctly) fail later because we return an invalid PID, which matches our invalid infra container. Signed-off-by: Peter Hunt <pehunt@redhat.com>

view details

Sascha Grunert

commit sha f0d987acb9b7cd5d3ae6c369d32c43e9db21a845

Switch to containers/common for AppArmor Most of the source code previously part of libpod is now in containers/common, which means that we can switch over here, too. Signed-off-by: Sascha Grunert <sgrunert@suse.com>

view details

Sascha Grunert

commit sha 7b942ed739b6688aba1d1ff06da6a64f74a72ccd

Remove git-validation in favor of prow/golangci-lint The whitespace checks are mostly done by our linters and the DCO verification will be done by prow. This means we can remove git-validation if we agree on skipping the git commit message check. Signed-off-by: Sascha Grunert <sgrunert@suse.com>

view details

Urvashi Mohnani

commit sha 6a3f71112ff79af8fa06db001b0117281ccd811e

Code clean up in containers_create_linux.go Noticed there was a TODO to assign GetSecurityContext() a variable and use that through out the create function. Signed-off-by: Urvashi Mohnani <umohnani@redhat.com>

view details

Jianzhu Zhang

commit sha 5011a7b2fef5ad5357a5a2d7e40a70a019e269cb

added irq smp balance and cpu cfs quota control Signed-off-by: Jianzhu Zhang <jianzzha@redhat.com>

view details

Wong Hoi Sing Edison

commit sha f45c631ab8b9b5f1f5920acc421dbdfb41f896dc

Update nix pin with `make nixpkgs` Also sync nix `packageOverrides` across skopeo/buildah/podman/cri-o for utilizing local build cache. Signed-off-by: Wong Hoi Sing Edison <hswong3i@gmail.com>

view details

OpenShift Merge Robot

commit sha 9dcd6cf14eed97c814d8bd6b6959878fc1399114

Merge pull request #4101 from haircommander/fix-ns-error managed ns: ignore `PID not initialized` on sandbox creation

view details

Antonio Ojea

commit sha 827eb0bfccb80873a3c3c5f41093a99d06cd9dc8

Revert "dual stack portmap support" This reverts commit f97ad7fd3fb3f0901e70a45e7caa57724715ce6c. It turns out this PR uncovered some issues on the port manager code we are vendoring. Signed-off-by: Antonio Ojea <aojea@redhat.com>

view details

OpenShift Merge Robot

commit sha 1b33acd9cf0865565821aaf8a00f62a8d28f05f1

Merge pull request #4130 from aojea/rev_dual Revert "dual stack portmap support"

view details

Peter Hunt

commit sha be9e42b7010803346df24c374d98c50de1ae7d29

Merge pull request #4109 from saschagrunert/containers-common Switch to containers/common for AppArmor

view details

Peter Hunt

commit sha 8152e00f31c86409622236121260dc028dfeb3c6

config: set internal RootConfig to default storage if not specified After we pull in the initial config, it is our source of truth for telling the world where our container storage is in particular, if we, say, have an empty `storage` entry, we will return `StorageDriver: ""` on an Inspect request the problem is, that is a lie. c/storage populates defaults for us, so we actually use overlay in that scenerio. we don't encounter this normally, because if the toml field isn't specified (as it isn't by default), then we inherit the information from the default config However, if a user (or an ignition config) overrides those fields to empty, we will listen to it as the source of truth, and never update to what is actually being used Fix this by inheriting the values from c/storage on the validation step. Signed-off-by: Peter Hunt <pehunt@redhat.com>

view details

Sascha Grunert

commit sha 4a3f8b87d36688579190a846a6f3500b85bd47de

Vendor Kubernetes v1.19.0 Signed-off-by: Sascha Grunert <sgrunert@suse.com>

view details

Sascha Grunert

commit sha b6db1d8a0b0ddb1777e0c2cae6124d10e7fcbacb

Fix pinns compilation for TEMP_FAILURE_RETRY In case the macro is not available we now define it on our own in the utils. Signed-off-by: Sascha Grunert <sgrunert@suse.com>

view details

OpenShift Merge Robot

commit sha 60a56f25ace7c09b2cf4086598a2321f294780b5

Merge pull request #4022 from jianzzha/jz-disable-irq added irq smp balance and cpu cfs quota control

view details

Peter Hunt

commit sha 635ab5f5d1f6978d4b45a888913f76c78ac7050a

oci: improve error message for verifyPid() Signed-off-by: Peter Hunt <pehunt@redhat.com>

view details

Peter Hunt

commit sha bc9dd6fe2949912af443bd76129a5a64102f0c0c

test: deflake stats test it is much less likely two containers will use the same amount of memory if they're different containers Signed-off-by: Peter Hunt <pehunt@redhat.com>

view details

Fabiano Fidêncio

commit sha b66da412d2a09eac0cde7c62bba711ee5fa48b8c

Revert "runtime_vm: Cleanup process when the Container is Stopped" This reverts commit 814c1bb01e84d6e42cd01b5957cad6e441228fa5. We cannot simply delete the container when its status changes to stopped. The intention of this fix is okay-ish, but implemented in the wrong layer. What containerd does is calling Shutdown(), when the *pod* is finished, and that's what we should do as well. Signed-off-by: Fabiano Fidêncio <fidencio@redhat.com>

view details

Peter Hunt

commit sha 525d5b760a31a566ef668b692a4e5efb00bf980e

sandbox: ignore enoent on shm unmount as it can be unmounted multiple times and should not result in an error Signed-off-by: Peter Hunt <pehunt@redhat.com>

view details

Kir Kolyshkin

commit sha 9925188dd54b248568a20366bb627401a15932b5

pinNamespaces: use string concat instead of fmt.Sprintf It is faster and also easier to read. Signed-off-by: Kir Kolyshkin <kolyshkin@gmail.com>

view details

Kir Kolyshkin

commit sha 2b5a80d57ff6de1f8c30333499b164bf1089ae4b

pinNamespaces: set capacity for returnedNamespaces We know the size of the slice already, so let's set its capacity in advance. Signed-off-by: Kir Kolyshkin <kolyshkin@gmail.com>

view details

push time in 2 months

PR opened cri-o/cri-o

Reviewers
update install linke

<!-- Thanks for sending a pull request!

Please be aware that we're following the Kubernetes guidelines of contributing to this project. This means that we have to use this mandatory template for all of our pull requests.

Please also make sure you've read and understood our contributing guidelines (https://github.com/cri-o/cri-o/blob/master/CONTRIBUTING.md) as well as ensuring that all your commits are signed with git commit -s.

Here are some additional tips for you:

  • If this is your first time, please read our contributor guidelines: https://git.k8s.io/community/contributors/guide#your-first-contribution and developer guide https://git.k8s.io/community/contributors/devel/development.md#development-guide
  • Please label this pull request according to what type of issue you are addressing, especially if this is a release targeted pull request. For reference on required PR/issue labels, read here: https://git.k8s.io/community/contributors/devel/sig-release/release.md#issuepr-kind-label
  • If you want faster PR reviews, read how: https://git.k8s.io/community/contributors/guide/pull-requests.md#best-practices-for-faster-reviews
  • If the PR is unfinished, see how to mark it: https://git.k8s.io/community/contributors/guide/pull-requests.md#marking-unfinished-pull-requests -->

What type of PR is this?

<!-- Uncomment only one /kind <> line, hit enter to put that in a new line, and remove leading whitespace from that line: -->

/kind api-change /kind bug /kind cleanup /kind dependency-change /kind deprecation /kind design /kind documentation /kind failing-test /kind feature /kind flake

What this PR does / why we need it:

Which issue(s) this PR fixes:

<!-- Automatically closes linked issue when PR is merged. Usage: Fixes #<issue number>, or Fixes (paste link of issue). -->

<!-- Fixes # or None -->

Special notes for your reviewer:

Does this PR introduce a user-facing change?

<!-- If no, just write None in the release-note block below. If yes, a release note is required: Enter your extended release note in the block below. If the PR requires additional action from users switching to the new release, include the string "action required".

For more information on release notes see: https://git.k8s.io/community/contributors/guide/release-notes.md -->

update broken link for install cri-o
+1 -1

0 comment

1 changed file

pr created time in 2 months

create barnchlovebaby979/cri-o

branch : setup

created branch time in 2 months

PR opened kubernetes/website

update README-ko.md

<!-- 🛈

Hello!

Remember to ADD A DESCRIPTION and delete this note before submitting your pull request. The description should explain what will change, and why.

PLEASE title the FIRST commit appropriately, so that if you squash all your commits into one, the combined commit message makes sense. For overall help on editing and submitting pull requests, visit: https://kubernetes.io/docs/contribute/start/#improve-existing-content

Use the default base branch, “master”, if you're documenting existing features in the English localization.

If you're working on a different localization (not English), or you are documenting a feature that will be part of a future release, see https://kubernetes.io/docs/contribute/new-content/overview/#choose-which-git-branch-to-use for advice.

-->

+1 -1

0 comment

1 changed file

pr created time in 2 months

create barnchlovebaby979/website

branch : br5

created branch time in 2 months

PR opened kubernetes/website

README-ko.md

<!-- 🛈

Hello!

Remember to ADD A DESCRIPTION and delete this note before submitting your pull request. The description should explain what will change, and why.

PLEASE title the FIRST commit appropriately, so that if you squash all your commits into one, the combined commit message makes sense. For overall help on editing and submitting pull requests, visit: https://kubernetes.io/docs/contribute/start/#improve-existing-content

Use the default base branch, “master”, if you're documenting existing features in the English localization.

If you're working on a different localization (not English), or you are documenting a feature that will be part of a future release, see https://kubernetes.io/docs/contribute/new-content/overview/#choose-which-git-branch-to-use for advice.

-->

+1 -1

0 comment

1 changed file

pr created time in 2 months

create barnchlovebaby979/website

branch : br4

created branch time in 2 months

PR opened kubernetes/website

update README-it.md

<!-- 🛈

Hello!

Remember to ADD A DESCRIPTION and delete this note before submitting your pull request. The description should explain what will change, and why.

PLEASE title the FIRST commit appropriately, so that if you squash all your commits into one, the combined commit message makes sense. For overall help on editing and submitting pull requests, visit: https://kubernetes.io/docs/contribute/start/#improve-existing-content

Use the default base branch, “master”, if you're documenting existing features in the English localization.

If you're working on a different localization (not English), or you are documenting a feature that will be part of a future release, see https://kubernetes.io/docs/contribute/new-content/overview/#choose-which-git-branch-to-use for advice.

-->

+1 -1

0 comment

1 changed file

pr created time in 2 months

create barnchlovebaby979/website

branch : br3

created branch time in 2 months

PR opened kubernetes/website

update README-id.md

<!-- 🛈

Hello!

Remember to ADD A DESCRIPTION and delete this note before submitting your pull request. The description should explain what will change, and why.

PLEASE title the FIRST commit appropriately, so that if you squash all your commits into one, the combined commit message makes sense. For overall help on editing and submitting pull requests, visit: https://kubernetes.io/docs/contribute/start/#improve-existing-content

Use the default base branch, “master”, if you're documenting existing features in the English localization.

If you're working on a different localization (not English), or you are documenting a feature that will be part of a future release, see https://kubernetes.io/docs/contribute/new-content/overview/#choose-which-git-branch-to-use for advice.

-->

+1 -1

0 comment

1 changed file

pr created time in 2 months

create barnchlovebaby979/website

branch : br2

created branch time in 2 months

PR opened kubernetes/website

update link

<!-- 🛈

Hello!

Remember to ADD A DESCRIPTION and delete this note before submitting your pull request. The description should explain what will change, and why.

PLEASE title the FIRST commit appropriately, so that if you squash all your commits into one, the combined commit message makes sense. For overall help on editing and submitting pull requests, visit: https://kubernetes.io/docs/contribute/start/#improve-existing-content

Use the default base branch, “master”, if you're documenting existing features in the English localization.

If you're working on a different localization (not English), or you are documenting a feature that will be part of a future release, see https://kubernetes.io/docs/contribute/new-content/overview/#choose-which-git-branch-to-use for advice.

-->

+2 -2

0 comment

1 changed file

pr created time in 2 months

create barnchlovebaby979/website

branch : br1

created branch time in 2 months

push eventlovebaby979/website

Monis Khan

commit sha 45551e8cba081a8da661a26c22ab6a9af856ad5b

Remove support for basic authentication Signed-off-by: Monis Khan <mok@vmware.com>

view details

Kevin Taylor

commit sha 4ed975af84f560863711a1abad50058726123ccb

Remove reference to VolumeSubpathEnvExpansion feature gate

view details

Monis Khan

commit sha 18664c0fff1cac2bae484d5284fb90ed3ae1c4a3

zh: remove support for basic authentication Signed-off-by: Monis Khan <mok@vmware.com>

view details

Savitha Raghunathan

commit sha 42fbd6e78924c9dd7e97dfc3246211817f53f790

config changes to prepare for v1.19 release Change config on dev-1.19 branch to prepare for v1.19 release

view details

Kubernetes Prow Robot

commit sha 2cb47cb2e13f5f49682081a1286653e6be17f9db

Merge pull request #20847 from savitharaghunathan/dev-1.19 Changing config.toml on dev-1.19 branch to prepare for v1.19 release

view details

Savitha Raghunathan

commit sha ea8179d29dcfc199bc22cf0b81cb010e8be24084

Merge remote-tracking branch 'upstream/master' into dev-1.19

view details

Kubernetes Prow Robot

commit sha 8e4d1d918d52a3bc80f459ef7ad24409c03a3df5

Merge pull request #20896 from savitharaghunathan/merged-master-dev-1.19 Branch sync - Merge master with dev 1.19

view details

Savitha Raghunathan

commit sha 1f08c931df548f0b2c54fd12f1accd1c420263ce

Merge remote-tracking branch 'upstream/master' into dev-1.19

view details

Kubernetes Prow Robot

commit sha 32d7f11a95375065a5afe48a916c95c3f774d4c6

Merge pull request #21073 from savitharaghunathan/merged-master-dev-1.19 Branch sync - Merge master with dev 1.19

view details

Savitha Raghunathan

commit sha 6311db5da4c100abc3310dfec687f190b65ca702

Merge remote-tracking branch 'upstream/master' into dev-1.19

view details

Kubernetes Prow Robot

commit sha 0061388373879e8659cf0e5f4860c3e1491411c7

Merge pull request #21214 from savitharaghunathan/merged-master-dev-1.19 Branch sync - Merge master with dev 1.19

view details

David Schott

commit sha e01349dc91777cb885d6bb6d42e3df3061f3fd23

updating Windows networking section with new features

view details

Ed Bartosh

commit sha 33468aac5a849cded1957e894f5bf5234c9cc7ac

Promote HugePageStorageMediumSize feature to Beta This is a documentation update for promoting multiple sizes hugepages future to Beta.

view details

Alex Wang

commit sha 4439f795f8777e5803a0f970cae532fef3671b87

update non preempt beta

view details

Savitha Raghunathan

commit sha f1966fe56ac53b3eb9c6e06544b17d2e935057be

Merge remote-tracking branch 'upstream/master' into dev-1.19

view details

Kubernetes Prow Robot

commit sha 696c8731106b657fed92fbc0a4abef369a93f4de

Merge pull request #21604 from savitharaghunathan/merged-master-dev-1.19 Branch sync - Merge master with dev 1.19

view details

Qiming Teng

commit sha 33d2138c2dffc5cfb46eae63991647e3468815fa

Mark RotateKubeletClientCertificate GA

view details

Qiming Teng

commit sha 358a3613467ca2a71cae65c3823670629da8e654

ServiceAppProtocol is beta in 1.19

view details

Qiming Teng

commit sha 58c152a9a8e7a3202151cb160b9e584f23030328

Mark StreamingProxyRedirects deprecated in 1.19

view details

Weiping Cai

commit sha cf3becadff9eecc03e995a3f0ccfead0b2487eac

use kubectl create deployment to create deployment with --replicas and --port. Signed-off-by: Weiping Cai <weiping.cai@daocloud.io>

view details

push time in 2 months

push eventlovebaby979/cri-o

Peter Hunt

commit sha 9a1490531fcb48f8903485a1781779f5bc2db9d8

managed ns: report namespace cleanup failure by default Signed-off-by: Peter Hunt <pehunt@redhat.com>

view details

Sascha Grunert

commit sha 017e62dc1d4cd56db31f3ed675c5ed3bf0e1aed4

Unset GOSUMDB when vendoring If the GOSUMDB cache is not up to date remotely a vendoring errors with: ``` go: github.com/containers/common@v0.14.7/go.mod: verifying module: invalid GOSUMDB: malformed verifier id ``` To aviod such failures in the future we now unset the GOSUMDB variable which forces golang to use the plain upstream address. Signed-off-by: Sascha Grunert <sgrunert@suse.com>

view details

OpenShift Merge Robot

commit sha ff2b2e20d239184ed30cadab0635e733de17497e

Merge pull request #4108 from saschagrunert/gosumdb Unset GOSUMDB when vendoring

view details

Peter Hunt

commit sha 773f6b0b5eddf3716e6055484dabef4ef493fb9d

branch forward: stop on rc turns out, it is a nice feature to stop the fast forward on a release candidate. return to this behavior Signed-off-by: Peter Hunt <pehunt@redhat.com>

view details

OpenShift Merge Robot

commit sha 20e629d1320278417ce54dd74b710dee0e979fbe

Merge pull request #4102 from haircommander/manage-cleanup-log managed ns: report namespace cleanup failure by default

view details

Mrunal Patel

commit sha a81c0adc888b57b7f33f7b10250845f78c067db8

Merge pull request #4122 from haircommander/release-branch-disable branch forward: stop on rc

view details

push time in 2 months

fork lovebaby979/cri-o

Open Container Initiative-based implementation of Kubernetes Container Runtime Interface

https://cri-o.io

fork in 2 months

issue openedkata-containers/runtime

Failed to check if grpc server is working: rpc error: code = Unavailable desc = transport is closing

Description of problem

kubectl describe pod podname Failed create pod sandbox: rpc error: code = Unknown desc = container create failed: Failed to check if grpc server is working: rpc error: code = Unavailable desc = transport is closing

Run kata with kubernetes.

How to check problems?

created time in 2 months

fork lovebaby979/website

Kubernetes website and documentation repo:

https://kubernetes.io

fork in 2 months

fork lovebaby979/documentation

Kata Containers version 1.x documentation (for version 2.x see https://github.com/kata-containers/kata-containers).

https://katacontainers.io/

fork in 2 months

PR opened kubernetes/website

update kubernetes concept

<!-- 🛈

Hello!

Remember to ADD A DESCRIPTION and delete this note before submitting your pull request. The description should explain what will change, and why.

PLEASE title the FIRST commit appropriately, so that if you squash all your commits into one, the combined commit message makes sense. For overall help on editing and submitting pull requests, visit: https://kubernetes.io/docs/contribute/start/#improve-existing-content

Use the default base branch, “master”, if you're documenting existing features in the English localization.

If you're working on a different localization (not English), or you are documenting a feature that will be part of a future release, see https://kubernetes.io/docs/contribute/new-content/overview/#choose-which-git-branch-to-use for advice.

--> update kubernetes concepts link

+3 -3

0 comment

1 changed file

pr created time in 3 months

push eventlovebaby979/website

wangjibao.lc

commit sha af6da61e645e1a9627f074d9a2727713eadcdbc6

update kubernetes concept

view details

push time in 3 months

PR opened kubernetes/website

update minikube document

<!-- 🛈

Hello!

Remember to ADD A DESCRIPTION and delete this note before submitting your pull request. The description should explain what will change, and why.

PLEASE title the FIRST commit appropriately, so that if you squash all your commits into one, the combined commit message makes sense. For overall help on editing and submitting pull requests, visit: https://kubernetes.io/docs/contribute/start/#improve-existing-content

Use the default base branch, “master”, if you're documenting existing features in the English localization.

If you're working on a different localization (not English), or you are documenting a feature that will be part of a future release, see https://kubernetes.io/docs/contribute/new-content/overview/#choose-which-git-branch-to-use for advice.

--> update minikube document link

+3 -3

0 comment

1 changed file

pr created time in 3 months

create barnchlovebaby979/website

branch : minikube

created branch time in 3 months

push eventlovebaby979/website

Miquel Ortega

commit sha f3e22cbcac21fa14b001f6a89453621db0c93580

First big translation on doc/contribute/start

view details

Miquel Ramon Ortega Tido

commit sha ee9124e74a60e353ae567ff9e6d0044922702817

Finished first translation on doc/contribute/start

view details

wolmi

commit sha e05930dce2cc6a8c694f668a5a596faf9b01e732

Apply suggestions from code review Co-Authored-By: Victor Morales <chipahuac@hotmail.com>

view details

wolmi

commit sha 3a591974462074133aa6d3d724e4c413fb11d7e2

Removed new line that could break the link

view details

wolmi

commit sha 732effb79afbc0e549f0bd73e2e09605342f9249

Apply suggestions from code review Co-Authored-By: Rael Garcia <rael@rael.io>

view details

wolmi

commit sha 58c73205bd1cdd70718869006354251c74fc9819

Removed new-line to fix preview

view details

wolmi

commit sha c30d1f203e31f2a8c9e1b6da697a1117b591836f

Apply suggestions from code review Co-Authored-By: Victor Morales <chipahuac@hotmail.com>

view details

Cheikhrouhou ines

commit sha a3f977aaec05b09b5fe20c749703c7ece1e8546c

translate service account fr

view details

Enrique Medina Montenegro

commit sha eab4f2199e6c8170fbb3bc9a7f175e8f9fd91be8

Spanish Translation

view details

Cheikhrouhou ines

commit sha 496fad77bbf9a1362c332fdfca26f7c876532c02

renaming and fix for service account fr

view details

icheikhrouhou

commit sha 40496c2b7d8e2dc9f47f2da21c1ede2db6b93420

fix translate configure service account

view details

lou-lan

commit sha 9abcf6805bc513ee0e1a262a265e2e35d1362b6a

Fix minikube image 'project:hello-minikube-zero-install' has been suspended.

view details

lou-lan

commit sha bdc18d99f053aa0c1a7db2d127cc8a59cc73c032

Fix minikube image 'project:hello-minikube-zero-install' has been suspended.

view details

Hector Sam

commit sha 841db869b22296feeb711a9e82a0198947822899

Lang: FR, Removing announcement and deprecationwarning

view details

Rajakavitha1

commit sha f5ec0e5db4e8606e8627e5cabca3c79ea33ce5f7

Removing Rajakavitha1 from the approvers list It has been a pleasure working with the SIG-Docs team.

view details

Ori Hoch

commit sha 527960a0925287d80fc7840de4ffafb23f065732

volume_attributes is now volume_context in CSI spec this is reflected in the code as well: https://github.com/kubernetes/kubernetes/blob/master/pkg/volume/csi/csi_client.go#L52

view details

Weiping Cai

commit sha 5513c60b543026641e72905bec44ce58b343702b

add define interdependent environment variables page Signed-off-by: Weiping Cai <weiping.cai@daocloud.io>

view details

Johannes M. Scheuermann

commit sha 8308aabb860e07e4a826433bd9819369acbdc486

Add documentation for API server health checks

view details

Weiping Cai

commit sha 1253c3b39e632ea86d18b1d08534feb0192c0abf

fix UNCHANGE_REFERENCE to UNCHANGED_REFERENCE,and use you to replace we Signed-off-by: Weiping Cai <weiping.cai@daocloud.io>

view details

Richard Mokua

commit sha 9adc2c7c6c0347dc88ebd3a8fbdcfba100e5711b

Update audit.md

view details

push time in 3 months

PR opened kubernetes-sigs/apiserver-builder-alpha

update documnet

repair broken link

+1 -1

0 comment

1 changed file

pr created time in 3 months

push eventlovebaby979/apiserver-builder-alpha

wangjibao.lc

commit sha 842547a41bc76b24f0ec2754a8e3644c296a2819

update documnet

view details

push time in 3 months

create barnchlovebaby979/apiserver-builder-alpha

branch : config

created branch time in 3 months

PR opened kubernetes-sigs/apiserver-builder-alpha

update api docs

update api building docs

+2 -2

0 comment

1 changed file

pr created time in 3 months

create barnchlovebaby979/apiserver-builder-alpha

branch : api-dos

created branch time in 3 months

issue openedkubernetes-sigs/controller-runtime

client delete job,but pod not delete

delete job created by ctx, but pod created by job was not deleted. delete job code: getJob := &batchv1.Job{} myErr := r.Get(ctx, types.NamespacedName{Namespace: "csf", Name: jobName}, getJob) if myErr != nil && !api_errors.IsNotFound(myErr) { r.Log.WithValues("Reconcile CsfTemplate get job fail!") return false, myErr } else if api_errors.IsNotFound(myErr) { return true, nil } errDel := r.Delete(ctx, getJob) if errDel != nil { r.Log.Error(errDel, " deleteJob fail! Namespace["+"csf"+"],JobName["+jobName+"]\n", errDel.Error()) }else{ r.Log.Info(" deleteJob success! Namespace["+"csf"+"],JobName["+jobName+"]\n") }

created time in 3 months

fork lovebaby979/client-go

Go client for Kubernetes.

fork in 3 months

fork lovebaby979/kube-openapi

Kubernetes OpenAPI spec generation & serving

fork in 3 months

fork lovebaby979/kubernetes

Production-Grade Container Scheduling and Management

https://kubernetes.io

fork in 3 months

create barnchlovebaby979/apiserver-builder-alpha

branch : cheatsheet2

created branch time in 3 months

fork lovebaby979/enhancements

Enhancements tracking repo for Kubernetes

fork in 3 months

push eventlovebaby979/apiserver-builder-alpha

rivencxl

commit sha 242417007a2fd55281f9a288917927b6c14d4869

fix duplicate add etcd

view details

Kubernetes Prow Robot

commit sha e156308a4b34d8dc248b87d7024cfe112af949df

Merge pull request #505 from rivencxl/master fix duplicate add etcd

view details

yue9944882

commit sha 14a40c821b362e31549c3c20cfa269150d585ccd

bump mod dependency to 1.18.4

view details

yue9944882

commit sha 3ab6bdad0cb268596398118b3b0983b35bceba01

aligns interface changes

view details

yue9944882

commit sha 0f4db18ea4c423b83f9537f9abe0a8f933cf149b

fixes test compiliation

view details

yue9944882

commit sha 95dca1d34e91d6e76c50fa4f272a77f573fd7558

bump v1.18.0

view details

yue9944882

commit sha d5fdf8c1b65a7c6068806b540998889ec5114c36

fixes code template

view details

Kubernetes Prow Robot

commit sha 4cc6c2f345e4d7176459c83c11edfe0e659dbb32

Merge pull request #508 from yue9944882/bump-k8s-1-18 Bump mod dependency to 1.18.4

view details

yue9944882

commit sha cdc8cfb63740e70be8bd23a8e0eac733f9b98611

pre-install autoscalingv1 scale to scheme explicitly

view details

Kubernetes Prow Robot

commit sha a3718943ef91ffd65400e23bd71e80b7a372f87e

Merge pull request #510 from yue9944882/register-autoscaling-scale-subresource-scheme Pre-install autoscalingv1 scale to scheme explicitly

view details

yue9944882

commit sha ebff1f2c8a61ad91019b4829ca5ad711a8775d48

tap

view details

Kubernetes Prow Robot

commit sha 3b9a0469128dd20406f97f1ce812ed7581796587

Merge pull request #513 from yue9944882/homebrew-integration Initial homebrew integration for simplifying installation

view details

push time in 3 months

more