- name: workload-socket
              mountPath: /var/run/secrets/workload-spiffe-uds
            - name: credential-socket
              mountPath: /var/run/secrets/credential-uds
            {{- if eq .Values.global.caName "GkeWorkloadCertificate" }}
            - name: gke-workload-certificate
              mountPath: /var/run/secrets/workload-spiffe-credentials
              readOnly: true

        "description": "ExecAction describes a \"run in container\" action.",
        "properties": {
          "command": {

		}
	}

	t.Run("generated-claim-name", func(t *testing.T) {
		for _, spec := range []*core.PodSpec{&goodClaimTemplate, &goodClaimReference} {
			claimName := spec.ResourceClaims[0].Name
			t.Run(claimName, func(t *testing.T) {
				for _, podMeta := range []*metav1.ObjectMeta{shortPodName, brokenPodName} {
					t.Run(podMeta.Name, func(t *testing.T) {

        "properties": {
          "potentialNodes": {
            "description": "PotentialNodes lists nodes where the Pod might be able to run.\n\nThe size of this field is limited to 128. This is large enough for many clusters. Larger clusters may need more attempts to find a node that suits all pending resources. This may get increased in the future, but not reduced.",

*   TensorBoard fixes: graphs with only one data point, Nan values, reload
    button and auto-reload, tooltips in scalar charts, run filtering, stable
    colors
*   Tensorboard graph visualizer now supports run metadata. Clicking on nodes
    while viewing a stats for a particular run will show runtime statistics,
    such as memory or compute usage. Unused nodes will be faded out.

## Thanks to our Contributors

- Fix kubectl diff so it doesn't actually persist patches ([#89795](https://github.com/kubernetes/kubernetes/pull/89795), [@julianvmodesto](https://github.com/julianvmodesto)) [SIG CLI and Testing]
- Fix kubectl run  --dry-run client  ignore namespace ([#90785](https://github.com/kubernetes/kubernetes/pull/90785), [@zhouya0](https://github.com/zhouya0)) [SIG CLI]

  ```

If more than one session.run call is simultaneously trying to compute `b`
the values of `a` will be gathered, non-deterministically concatenated
along the first axis, and only one thread will run the computation.

Assumes that all arguments of the function are Tensors which will be batched
along their first dimension.

Arguments that are captured, are not batched. The session.run call which does

Bodies in straight Lines, and that these Shadows have three parallel
Fringes, Bands or Ranks of colour'd Light adjacent to them. But if the
Hole be enlarged the Fringes grow broad and run into one another, so
that they cannot be distinguish'd. These broad Shadows and Fringes have
been reckon'd by some to proceed from the ordinary refraction of the

              details at: https://istio.io/docs/reference/config/networking/proxy-config.html'
            properties:
              concurrency:
                description: The number of worker threads to run.
                format: int32
                minimum: 0
                nullable: true
                type: integer
              environmentVariables:
                additionalProperties:

		{"UserHomeDir", Func, 12},
		{"WriteFile", Func, 16},
	},
	"os/exec": {
		{"(*Cmd).CombinedOutput", Method, 0},
		{"(*Cmd).Environ", Method, 19},
		{"(*Cmd).Output", Method, 0},
		{"(*Cmd).Run", Method, 0},
		{"(*Cmd).Start", Method, 0},
		{"(*Cmd).StderrPipe", Method, 0},
		{"(*Cmd).StdinPipe", Method, 0},
		{"(*Cmd).StdoutPipe", Method, 0},
		{"(*Cmd).String", Method, 13},