Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Blog about discoverable KMS #2534

Open
mudler opened this issue May 6, 2024 · 2 comments
Open

Blog about discoverable KMS #2534

mudler opened this issue May 6, 2024 · 2 comments
Assignees
Labels
lane/press triage Add this label to issues that should be triaged and prioretized in the next planning call

Comments

@mudler
Copy link
Member

mudler commented May 6, 2024

Since we have added Discoverable KMS with p2p, we can create a blog post about it and share how does it work, what problems solves, etc.

@mudler mudler changed the title [DK] Blog about discoverable KMS Blog about discoverable KMS May 6, 2024
@ci-robbot ci-robbot added the triage Add this label to issues that should be triaged and prioretized in the next planning call label May 6, 2024
@ci-robbot
Copy link
Collaborator

Hello, I'm an experiment bot created by @mudler and @jimmykarily. I just wanted to let you know that I have added the 'triage' label to your issue 2534. This will help other members of the community to understand that the issue has been reviewed and is awaiting further action. Please make sure to provide a clear description of the issue and mention the versions of the relevant artifacts being used to ensure that your issue meets the project's guidelines. If you need any further assistance, feel free to ask.

@ci-robbot
Copy link
Collaborator

Hello, I am an experimental bot assisting in ticket auditing for the Github project. Thank you for proposing a blog post about the Discoverable KMS feature.

In order to ensure that the issue adheres to the project's guidelines, please provide a brief description of the issue and, if it's a bug, steps to reproduce the issue. Additionally, kindly mention the versions of the relevant artifacts being used.

Once the issue meets these criteria, I will label it with 'triage' to indicate it has been reviewed. If it is not clear or missing any information, I will label it with 'add_label_to_github_issue' and provide more details.

Please understand that this auditing process is an experiment by @mudler and @jimmykarily, and I am here to help ensure the project's rules and guidelines are followed. Thank you for your understanding and collaboration.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lane/press triage Add this label to issues that should be triaged and prioretized in the next planning call
Projects
Status: Under review 🔍
Development

No branches or pull requests

3 participants