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

The SDK is very unfriendly for beginners.

Apart from the fact every program imports docker/docker (including docker-ce and kubernetes) and that redirects to moby/moby on the website, the default version you get from go is v1.13.1 and people just seem to import specific commits. The releases can not be seen on moby/moby but can be found on docker/engine however you can not import s

Bug report summary

Running the netdata-installer.sh as a non-root user produces instructions on how to escalate privilege for the apps plugin. The instructions cannot be cut and pasted into a shell as there are some extra escaping characters in front of the quotes.

To run apps.plugin with escalated capabilities:

    sudo chown root:amoss \"/home/amoss/netdata/dev-install/netdat

I feel like there could be a brush up on the minikube emojis,

minikube delete

its kind of weird in one emoji we have breaking heart and the one after is fire...

🔥  Removing /root/.minikube/machines/minikube ...
💔  The "minikube" cluster has been deleted.
🔥  Successfully deleted profile "minikube"

this specially looks weird when deleting multiple profiles

minikub

What kind of request is this (question/bug/enhancement/feature request):
doc bug/rfe

Other details that may be helpful:
Today we have generic doc's for enabling cluster level monitoring. Just a placeholder doc bug to extend that to resource requirements when monitoring at the project level.

When a container image tag is too long, it causes the fav and close icons to be shifted. Max width should be 120px - child span should be inline-block

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

rkt run ./mycontainer_image.aci.tar.gz fails with error run: invalid image string on valid container image but succeeds when image file is renamed (or symlinked) to mycontainer_image.aci.

IMHO it is unnecessary to enforce image file names to end with .aci.
Structure of the .ACI file is gzipped tarball (.tar.gz) and having images named as such allows browsing images file system with t

Upon running
skaffold run --enable-rpc -v info --rpc-http-port 51328 --filename skaffold.yaml
time="2019-08-07T11:51:11-07:00" level=info msg="Skaffold &{Version:v0.27.0 ConfigVersion:skaffold/v1beta8 GitVersion: GitCommit:6e9c61df6336540325b927071d62947b261a77bf GitTreeState:clean BuildDate:2019-04-12T17:58:53Z GoVersion:go1.11.8 Compiler:gc Platform:darwin/amd64}"

Expected behavior

Th

From #2046.

Auth has the most friction, and it will help a lot to report if Jib picked up some credentials and where if so. It will help cases like #2050 too.

The output of `oc new-build

[Request from summit]:

We should start a mailing list and inform subscribers with important events and timelines. Ex: moving moby tool from this repo to moby org.

There are very similar or identical dialer implementations in (at least) pkg/dialer, pkg/ttrpcutil, and runtime/v2/shim. It looks like there is potential to unify these into set of dialer functionality (probably in pkg/dialer).

Store pod and namespace name in the external identifiers of an endpoint.

https://github.com/cilium/cilium/blob/39dea0071d531e9c56cecf85ef26ccbb36682c5d/pkg/endpoint/api.go#L208

It will require changes in the API:
https://github.com/cilium/cilium/blob/39dea0071d531e9c56cecf85ef26ccbb36682c5d/api/v1/openapi.yaml#L841
https://github.com/cilium/cilium/blob/39dea0071d531e9c56cecf85ef26ccbb366

Version Kompose 1.18.0 (06a2e56)

My relevant docker_compose service looks like:

  gateway:
    image: "${AWS_ACCOUNT_ID}.dkr.ecr.${AWS_REGION}.amazonaws.com/${ECR_GATEWAY_REPO}:${TAG}"
    build: "${GATEWAY_MONOREPO_DIR}"
    ports:
      - "33000:4200"
    deploy:
      mode: replicated
      replicas: 1
      endpoint_mode: vip
    labels:
      kompose.service.type: loadb

this will very quickly get out of hand if we allow it, i realize we don't have principles written down anywhere but to date one of them has been that binaries 'just work' without having to do any configuration. currently a user must set FN_MAX_REQUEST_SIZE, FN_MAX_RESPONSE_SIZE -- neither of these should be required to run.

test case:

cd tests/fn-system-tests/
go test -v

this

Can you extend the try out in Installation.md to:

1. run a pouch container.
2. use an Ali or customer container instead of a Docker container.
   and
3. Ask user to log into the container and experience the vm like environment?

Edit the deployment section of the Pachyderm documentation.

I'm a bit confused about the registerOutputs call and what actually is considered an output.
The current documentation says this:

Components can define their own properties using registerOutputs. The Pulumi engine uses this information to display the logical outputs of the component. The call to registerOutputs also tells Pulumi that the resource is done registering children and should be c