kpng icon indicating copy to clipboard operation
kpng copied to clipboard

informal docs on how to run KPNG in ( cluster-lifecycle, kubeadm, kops, kubespray, openshift community, tanzu community edition, k3s, other offerings ...) ?

Open jayunit100 opened this issue 2 years ago • 4 comments

If someone wants to investigate what other projects we may want to update to be able to swap about the kube proxy.... this is a good long term initiative... goal would be, a series of blog posts or cncf posts on how to run KPNG in different environments. it might help us to get other folks testing/using it as an alternate.

  • blog post on how to run it in CAPI
  • blog post on how to run it in kind
  • blog post on how to run it in kubespray

jayunit100 avatar Jul 18 '22 15:07 jayunit100

/good-first-issue

jayunit100 avatar Jul 18 '22 15:07 jayunit100

@jayunit100: This request has been marked as suitable for new contributors.

Guidelines

Please ensure that the issue body includes answers to the following questions:

  • Why are we solving this issue?
  • To address this issue, are there any code changes? If there are code changes, what needs to be done in the code and what places can the assignee treat as reference points?
  • Does this issue have zero to low barrier of entry?
  • How can the assignee reach out to you for help?

For more details on the requirements of such an issue, please see here and ensure that they are met.

If this request no longer meets these requirements, the label can be removed by commenting with the /remove-good-first-issue command.

In response to this:

/good-first-issue

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

k8s-ci-robot avatar Jul 18 '22 15:07 k8s-ci-robot

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue or PR as fresh with /remove-lifecycle stale
  • Mark this issue or PR as rotten with /lifecycle rotten
  • Close this issue or PR with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

k8s-triage-robot avatar Oct 16 '22 16:10 k8s-triage-robot

/remove-lifecycle stale

knabben avatar Apr 04 '23 18:04 knabben