Possibility to add additional static string date to the created secret with CSI driver

[AswinT22]

At the moment the created secret can only contain values that have been fetched by the CSI driver. In use cases when we want to add some non-sensitive data as part of the secret we had to add those to the vault and fetch them along with the sensitive data.

I want to go from this

apiVersion: secrets-store.csi.x-k8s.io/v1alpha1
kind: SecretProviderClass
metadata:
  name: my-provider
spec:
  provider: vault 
  parameters:
    objects: |
      - objectName: "username"
        secretPath: "secret/data"
        secretKey: "username_from_vault"
      - objectName: "url"
        secretPath: "secret/data"
        secretKey: "url_from_vault"
      - objectName: "password"
        secretPath: "secret/data"
        secretKey: "password_from_vault"                    
  secretObjects:                              
    - data:
        - key: PASSWORD                        
          objectName: password      
        - key: USERNAME                        
          objectName: username
        - key: URL                        
          objectName: url                
      secretName: credentials    
      type: Opaque

to this

apiVersion: secrets-store.csi.x-k8s.io/v1alpha1
kind: SecretProviderClass
metadata:
  name: my-provider
spec:
  provider: vault 
  parameters:
    objects: |
      - objectName: "password"
        secretPath: "secret/data"
        secretKey: "password_from_vault"                    
  secretObjects:                              
    - data:
        - key: PASSWORD                        
          objectName: password 
      stringData:     # data under this will be added to the secret object along with the retrieved secrets 
        - key: USERNAME                        
          value: myusername
        - key: URL                        
          value: myurl                
      secretName: credentials    
      type: Opaque

[tam7t]

This sounds pretty similar to #948 and #938 which I think would be best solved through #963 (a generic way to split/mutate the data returned by the provider).

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle rotten
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

[k8s-ci-robot]

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to this:

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.