What happened:

If I modify a custom endpoint, the kubectl kubectl.kubernetes.io/last-applied-configuration annotation is mirrored to the generated endpoint slice

What you expected to happen:

Since the kubect last-applied-configuration tracks the status of the object, it shouldn't be mirrored since it doesn't apply to the generated object

How to reproduce it (as minimally

Feature idea summary

Cgroups plugin supports only proportional and max Block IO policies. We should support BFQ scheduler as well. Disk stats for the scheduler are in blkio.bfq.io_service_bytes and blkio.bfq.io_serviced files.

currently our make generate-docs creates this page

https://minikube.sigs.k8s.io/docs/contrib/tests/

which generates the site based on the Comments on the Test and validate the func,

I would like these descriptions to exaclty say what it is doing instead of a general text

validateBuildImage 
makes sures that

Any hover effects doesn't properly applied to all header elements (top line with cluster name and cluster menu). It seems that something placed on top of them and covers most of their height.

https://user-images.githubusercontent.com/9607060/108056014-cd186a00-7061-11eb-8ac0-5d01e206e636.mp4

In what area(s)?

/area runtime

/area operator
/area placement
/area docs
/area test-and-release

What version of Dapr?

1.2.0

Expected Behavior

1. Describe IN DETAIL the feature/behavior/change you would like to see.

Implement WarmPool.RenderTerraform()

2. Feel free to provide a design supporting your feature request.

/kind feature
/area terraform
/lifecycle frozen

A user on the #skaffold channel was encountering a puzzling error:

Hello,

I am new to skaffold, I am facing issue while execeuting skaffold build application via skaffold in BB pipelines.
I have tried to echo variables mentioned like  $TARGET , $DOCKER_REGISTRY
before execution all are properly set but still it end up in error .

Kindly provide pointers to fix it.

+ skaffold bu

The doc says

	// Unlike io.Writer.Write, Endpoint.Write transfers ownership of any bytes
	// successfully written to the Endpoint. That is, if a call to
	// Write(SlicePayload{data}) returns (n, err), it may retain data[:n], and
	// the caller should not use data[:n] after Write returns.

but the signature of Write has since changed. It no longer accepts a slice payload, so this

Environment:

• Jib version: 2.7.1
• Build tool: Maven
• OS: N/A

Description of the issue:

Invoking mvn jib:help results in error

[ERROR] Could not find goal 'help' in plugin com.google.cloud.tools:jib-maven-plugin:2.7.1 among available goals _skaffold-fail-if-jib-out-of-date, _skaffold-files-v2, _skaffold-init, _skaffold-package-goals, _skaffold-sync-map, build, 

This is a reminder for me or a task if anyone wants :P

Basically, The last two questions aren't really regex's questions.

To do:

• Move said questions to correct place.
• Add new regex questions (Python related!)?
• Maybe add a new ## Regex section, as it is a valuable skill

There are a lot of places in libcontainer/cgroups/fs where the usage of writeFile function can be optimised. For example here https://github.com/opencontainers/runc/blob/master/libcontainer/cgroups/fs/blkio.go#L44-L51
the function call to writeFile is made for each entry in the slice BlkioWeightDevice, which in turn opens and closes file for each entry. This can be optimised by joining al

Command: cortex debug exec API_NAME

Behavior: choose a running API pod (at random is ok if there are multiple), and run e.g. kubectl exec -it api-iris-classifier-6d866654f8-pwz62 --container api -- /bin/bash

This command should be executed in the manager container, similar to how the cortex cluster up command works. However unlike cortex cluster up, this command will require interact

Currently, Trivy traverses all paths and looks for all Gemfile.lock in a container image. However, the image sometimes has only Gemfile.lock and doesn't install gems listed in the Gemfile.lock. I think a gem should have *.gemspec file if it is installed. e.g. rake.gemspec has the information about rake.

To avoid false positives from Gemfile.lock, we are probably able to take advantage of `*