kubernetes

The RBAC docs say that Most resources are represented by a string representation of their name, such as “pods”, just as it appears in the URL for the relevant API endpoint. However, some Kubernetes APIs involve a “subresource”, such as the logs for a pod. […] To represent this in an RBAC role, use a … Read more

As mentioned here kubectl will never support variable substitution. You can create a helm chart for your app (yaml). It supports yaml template variables (among various other features). So you’ll be able to pass hostPath parameter based on development or production.

I checked the code in pkg/kubectl/cmd/apply.go and I think the following lines of code shows what’s behind the scene when you run kubectl apply -f: // Compute a three way strategic merge patch to send to server. patch, err := strategicpatch.CreateThreeWayMergePatch(original, modified, current, versionedObject, true) helper := resource.NewHelper(info.Client, info.Mapping) _, err = helper.Patch(info.Namespace, info.Name, api.StrategicMergePatchType, … Read more

The docs say it pretty well: When a Job completes, no more Pods are created, but the Pods are not deleted either. Keeping them around allows you to still view the logs of completed pods to check for errors, warnings, or other diagnostic output. The job object also remains after it is completed so that … Read more

ownerReferences has two purposes: Garbage collection: Refer to the answer of ymmt2005. Essentially all owners are considered for GC. Contrary to the accepted answer the controller field has no impact on GC. Adoption: The controller field prevents fighting over resources which are to be adopted. Consider a replica set. Usually, the replica set controller creates … Read more