Skip to content

Conversation

DanielHougaard
Copy link
Member

Description 📣

Documentation for the new secretName field for fetching a single secret using the InfisicalSecret CRD without using templates.

PR: Infisical/kubernetes-operator#10

Type ✨

  • Bug fix
  • New feature
  • Improvement
  • Breaking change
  • Documentation

@maidul98
Copy link
Collaborator

🎉 Snyk checks have passed. No issues have been found so far.

security/snyk check is complete. No issues have been found. (View Details)

Copy link
Contributor

@greptile-apps greptile-apps bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Greptile Summary

This PR adds documentation for a new secretName field in the InfisicalSecret Custom Resource Definition (CRD) for the Kubernetes operator. The field is optional and allows users to fetch a single specific secret from Infisical by name, rather than retrieving all secrets within the specified scope.

The change is purely documentation-focused, adding consistent explanatory comments across multiple authentication method examples in the docs/integrations/platforms/kubernetes/infisical-secret-crd.mdx file. Each example now includes:

secretName: <secret-name> # OPTIONAL: If you want to fetch a single Infisical secret, you can specify the secret name here. If not specified, all secrets in the specified scope will be fetched.

This documentation update corresponds to a feature implemented in the Kubernetes operator (referenced PR: Infisical/kubernetes-operator#10) and maintains backward compatibility - when secretName is not specified, the operator continues to fetch all secrets in the scope as before. The feature integrates with the existing authentication methods (Universal Auth, AWS IAM, GCP, Azure, Kubernetes, LDAP, Service Account, and Service Token) and provides more granular control over secret retrieval, which can improve performance and reduce resource usage when only a specific secret is needed.

Confidence score: 5/5

  • This PR is extremely safe to merge with no risk of breaking existing functionality
  • Score reflects that this is purely documentation with no code changes and maintains backward compatibility
  • No files require special attention as this is straightforward documentation enhancement

1 file reviewed, no comments

Edit Code Review Bot Settings | Greptile

@DanielHougaard DanielHougaard merged commit 1ed8794 into main Sep 19, 2025
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants