This issue was reported in the Kubernetes Security Audit Report

Description
The strconv.Atoi function parses an int - a machine dependent integer type, which, for 64-bit targets will be int64. There are places throughout the codebase where the result returned from strconv.Atoi

Bug report summary

After yesterday's incident, that we come to realise approved and merged code was corrupting the registry APIs, we prioritised the introduction of validations for the registry API on our CI, to block faulty PRs from going into our master branch

CC: @cosmix @cakrit

OS / Environment

Any

Netdata version (ouput of netdata -V)

Latest

Component

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 Provisioning Identity through SDS 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/master/tests/integration

The exact command to reproduce the issue:
this issue was part of #6103, and the exact command was /bin/bash -c \"sudo env PATH=/var/lib/minikube/binaries/v1.17.0:$PATH kubeadm config images pull --config /var/tmp/minikube/kubeadm.yaml\"

The full output of the command that failed:

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

Have a new needle in the server subgenerator for adding new log level configuration.

Motivation for or Use Case

hipster-labs/generator-jhipster-entity-audit#62 is a good example for the need.

Related issues or PR

**What kind of request is this (question/bug/enhan

Describe the bug
Mismatch between the unit formatting for prometheus.prometheusSpec.retentionSize and the official Prometheus doc.

Which chart:
stable/prometheus-operator

What happened:
The description of the prometheus.prometheusSpec.retentionSize in the README give 50GiB as an example, where

PR rancher/k3s#1192 adds the secret encryption config to k3s, we need to document how to use this feature

Issue Description

Type: feature request

Describe what happened (or what feature you want)

On the service details page, click the return page, and the entered search criteria disappear. You need to re-enter the search criteria every time you return to view the service details.

Describe what you expected to happen

Return to previous page to keep query criteria.

How t

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

Sample app deployed to GKE cluster

Actual behavior

1.FATA[0011] reading manifests: kubectl create: Running [kubectl --context create --dry-run -oyaml -f k8s-pod.yaml]: stdout , stderr: Unable to connect to the server: net/ht

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

Every kubeflow image should be scanned for security vulnerabilities.
It would be great to have a periodic security report.
Each of these images with vulnerability should be patched and updated.

What would you like to be added:
Deploy the ingress-nginx NodePort service as documented here.

Why is this needed:
To be able to deploy ingress-nginx not in the host-network.

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