Jira Description

As a PCP user I want to secure the connections to keystone service so that my data in flight is encripted and secure from MITM attacks.

Summary

This is the initial implementation for configuring TLS certificates in keystone-operator, this will likely follow the approach from RabbitMQ operator, but will also likely be integrated with the cert-manager operator.

Definition of Ready

When we can consider User Story to be Ready?

1. Defined clearly enough that all members of the team understand what needs to be done
2. Includes any required enabling specs. wire frames etc.
3. Fully meet INVEST criteria for User Stories
4. Dependencies identified and there is a clear strategy how they will be managed

Prerequisites

1. Initial architecture defined https://issues.redhat.com/browse/OSP-19016

Acceptance Criteria

What needs to be done for issue to be considered complete. It helps teams estimate, test and accomplish work. We can think about Acceptance Criteria as "what customer needs".

1. Prepare and merge a pull request for keystone-operator to configure the certificates

Definition of Done

When we can consider User Story to be Done?

Definition of Done can differ from team to team. It represents some quality standards, which the team commits to deliver. Done mean the feature has been developed, tested and meets all required acceptance tests. Ideally, Done means the feature could be shipped to a customer.

When creating your definition of done, think about including:

1. Tests are created
2. Documentation for the initial configuration is created
3. Pull request is merged to master branch of keystone-operator
4. Other services should be able to follow this approach, so parts of the implementation might go into lib-common