In our scheduler tests, we rely on a hard-coded instantiation of empty pluginSet for necessary extensionPoint. It'd be good to handle the instantiation dynamically, so every time we add a test, the author doesn't need to worry about whether the pluginSet for an extension point has been instantiated or not.

Here are some occurrences, but it would be good to search thoroughly:

⇒  ag

i see our bug template

<!---
When creating a bug report please:
- Verify first that your issue is not already reported on GitHub
- Test if the latest release and master branch are affected too.
- Provide a clear and concise description of what the bug is in "Bug report 
  summary" section.
- Try to provide as much information about your environment (OS distribution,
  running in con

There is a document describing how to migrate an existing etcd cluster from HTTP communication to encrypted HTTPS.
The document uses v2-based CLI, some of those commands have different args or output format in their v3 equivalent, and some of them (like etcdctl cluster-health) doesn't seem to exist in v3. The documen

Do you want to request a feature or report a bug?

Describe the feature request
We need to develop a test for the Kubernetes Services for Egress Traffic task in order to provide automated testing of the Istio.io website for future releases.

Example tests and the documentation for the framework can be found here: https://github.com/istio/istio/tree

currently it keeps printing the first time someone looks at it, it looks a bit scary
specially with word errors repeating 4 times.

Status:	
	machine: minikube
	pid: 48635
	route: 10.96.0.0/12 -> 172.17.0.2
	minikube: Running
	services: [hello-minikube1]
    errors: 
		minikube: no errors
		router: no errors
		loadbalancer emulator: no errors

I purpose if there is no erro

Move all Dockerfile samples to non-root user

Expected Behaviour

As an OpenFaaS end-user, I want to run all samples on my OpenFaaS cluster, even with the new non-root feature enabled.

Current Behaviour

I had some issues and talked on the slack channel with @hickeyma.
In the end the problem was me, not understanding the helm chart name and the release name.

So I had the following situation:
I didn't know in the beginning that the release name had to be unique within a namespace. I used the helm chart name as component name (copy, content, seo, orders etc.) and the release name initial for

Overview of the feature request

When having entities with many fields, having them in the entity-update.component.ts file could be tedious. Also, when coding side-by-side it will force me to duplicate my code for creating the form, updating the form and for creating the entity from form (those can be big methods).

**Motivation for or Use

What kind of request is this (question/bug/enhancement/feature request):
Documentation update/enhancement

Other details that may be helpful:
The documentation for recurring snapshots does not include information about including a custom ca option you can use in the s3backupconfg. It w

Opened via rancher/docs#2178 we use rancher/k3s for tracking docs currently as it's easier to manage on our boards.

What exactly does disable network policy do? From a user standpoint, I don’t see any docs on what the network policy is to begin with (google “k3s network policy” or search the docs page). So, I'm not not sure what is being disabled when I use the `--disa

Issue Description

Type: feature request

Describe what happened (or what feature you want)

In the service list, add a button in the operation bar to link to the corresponding subscriber details.

Describe what you expected to happen

How to reproduce it (as minimally and precisely as possible)

Tell us your environment

nacos 1.1.3

Anything else we ne

Hi, I'm Yevgeny Pats Founder of Fuzzit - Continuous fuzzing as a service platform.

We have a free plan for OSS and I would be happy to contribute a PR if that's interesting.
The PR will include the following

• go-fuzz fuzzers (This is generic step not-connected to fuzzit)
• Continuous Fuzzing of master branch which will generate new

Feature Description

At the last Vitess monthly meeting we discussed adding golangci-lint as a git hook, and the hosted service https://golangci.com/ as a GitHub check.

Expected behavior

I am trying to get out of a weird state which I believe is related to #1737. I expect skaffold delete to clean up my deployment.

Actual behavior

When I attempt to run skaffold delete I get an error:

error validating data: Valid

Hi.

To be able to use jib-core on environments where there is no Docker CLI installed, or programmatically (e.g. with Testcontainers), it would be helpful to be able to provide a custom implementation of DockerClient that will be using the REST API, for instance.

It seems to me that the interface will have the following methods:

• `load(ImageTarball, Cons

We are moving in the direction of having multiple config files like
https://github.com/kubeflow/kubeflow/blob/master/bootstrap/config/kfctl_gcp_iap.0.6.yaml
https://github.com/kubeflow/kubeflow/blob/master/bootstrap/config/kfctl_existing_arrikto.0.6.yaml

that specify different configurations of Kubeflow

We should add unittests that ensure consistency.

i.e. we should add a test that veri

What would you like to be added:
Support for deploying vSphere storage Container Storage Interface (CSI).
It' GA already.

https://github.com/kubernetes-sigs/vsphere-csi-driver
https://cloud-provider-vsphere.sigs.k8s.io/

It requires vSphere 6.7u3+

Why is this needed:

• The in-tree cloud provider for vSphere is deprecated.
• The CSI is the standard way to implement the Storage

Disclaimer: This is my blog post

There's not a lot of K3OS material out there, so I feel like this would be great until a K3 awesome list was made.

https://medium.com/@jamesdavidbohrman/self-registering-compact-k3os-clusters-to-rancher-server-via-cloud-init-d4a89028c1f8

The first few Google results for OpenShift alert documentation point to https://docs.openshift.com/online/dev_guide/notifications.html , which is now a dead link.

Please help Google point results to the right link, such as by redirecting from this URL to a valid one.

Description

Add Azure notebook to our SETUP doc.
I tested google colab and Azure notebook to run reco-repo without requiring creating any DSVM or compute by myself, and it works really well with simple tweaks to the notebooks (e.g. for some libs, should install manually).

I think it would be good to add at least Azure notebook to our SETUP doc, where users can easily test out our repo w/o

The deployment installs two services, frontend and frontend-external. Do we need to have two? Can we just have a single load balancer service?

Otherwise the logs of pilot show

        "pilot_conflict_inbound_listener": {
            "frontend-b64f4c9bb-jt4k6.micro": {
                "proxy": "frontend-b64f4c9bb-jt4k6.micro",
                "message": "Conflicting inbound listener:

Is this a bug report or feature request?

• Feature Request

What should the feature do:
Create a new document to explain the different settiong and options available in the Operator CRD

What is use case behind this feature:
We do not have this document, and although we have most of the things explained in the CRD file, it could be interesting to have this information also as a

https://kubernetes.github.io/ingress-nginx/user-guide/nginx-configuration/annotations/#mirror

Should be something like https://gist.github.com/aledbf/48237bd5d2dd23df4b9a2cf83d28d228, mirroring the traffic to an external site.

环境

版本和配置信息

[root@master1 traefik]# cat traefik-ingress-lb.yaml 
apiVersion: extensions/v1beta1
kind: DaemonSet
metadata:
  name: traefik-ingress-lb
  namespace: kube-system
  labels:
    k8s-app: traefik-ingress-lb
spec:
  template:
    metadata:
      labels:
        k8s-app: traefik-ingress-lb
        name: traefik-ingress-lb
    spec:
      terminationGracePeriodS

I love kubectx and kubens ! -- It saves me a ton of time, and I've been using it for a long time already.

Now there is also a new kid on the block. "Krew" https://github.com/kubernetes-sigs/krew. Krew is a plugin manager for kubectl and kubectx and kubens are excellent candidates for it.

Since kubectx and kubens work well, and are well tested I think it's worth porting them to this plugin sy