-
Notifications
You must be signed in to change notification settings - Fork 88
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
Fix outdated README file and add development notes #553
Conversation
Signed-off-by: Oleksandr Andriienko <oandriie@redhat.com>
Skipping CI for Draft Pull Request. |
Signed-off-by: Oleksandr Andriienko <oandriie@redhat.com>
Signed-off-by: Oleksandr Andriienko <oandriie@redhat.com>
Signed-off-by: Oleksandr Andriienko <oandriie@redhat.com>
Signed-off-by: Oleksandr Andriienko <oandriie@redhat.com>
Signed-off-by: Flavius Lacatusu <flacatus@redhat.com>
Co-authored-by: Yana Hontyk <yhontyk@redhat.com>
Co-authored-by: Yana Hontyk <yhontyk@redhat.com>
Co-authored-by: Yana Hontyk <yhontyk@redhat.com>
Co-authored-by: Yana Hontyk <yhontyk@redhat.com>
Co-authored-by: Yana Hontyk <yhontyk@redhat.com>
Co-authored-by: Yana Hontyk <yhontyk@redhat.com>
Co-authored-by: Yana Hontyk <yhontyk@redhat.com>
Co-authored-by: Yana Hontyk <yhontyk@redhat.com>
Co-authored-by: Yana Hontyk <yhontyk@redhat.com>
Co-authored-by: Yana Hontyk <yhontyk@redhat.com>
Co-authored-by: Yana Hontyk <yhontyk@redhat.com>
Co-authored-by: Yana Hontyk <yhontyk@redhat.com>
Co-authored-by: Yana Hontyk <yhontyk@redhat.com>
Co-authored-by: Yana Hontyk <yhontyk@redhat.com>
Co-authored-by: Yana Hontyk <yhontyk@redhat.com>
Co-authored-by: Yana Hontyk <yhontyk@redhat.com>
Co-authored-by: Yana Hontyk <yhontyk@redhat.com>
Co-authored-by: Yana Hontyk <yhontyk@redhat.com>
Co-authored-by: Yana Hontyk <yhontyk@redhat.com>
Co-authored-by: Yana Hontyk <yhontyk@redhat.com>
Co-authored-by: Yana Hontyk <yhontyk@redhat.com>
Co-authored-by: Yana Hontyk <yhontyk@redhat.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good job!
.ci/README.md
Outdated
@@ -0,0 +1,41 @@ | |||
### Che-Operator CI | |||
Che Operator currently support two CI launch cases for Pull Request checks: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
launch cases
-> flows
README.md
Outdated
You can also modify Kubernetes objects using the terminal. | ||
You can edit checluster CR object using the command-line editor: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What is the difference between these two?
README.md
Outdated
If cluster router uses certificate signed by self-signed one, then parent/root CA certificate should be added into corresponding config map of additional trusted certificates (see `serverTrustStoreConfigMapName` option). | ||
|
||
#### K8S | ||
|
||
By default self-signed certificates for Che will be generated automatically. | ||
If it is needed to use own certificates, create `che-tls` secret (see `k8s.tlsSecretName` option) with `key.crt` and `tls.crt` fields. In case of self-signed certificate `self-signed-certificate` secret should be created with public part of CA certificate under `ca.crt` key in secret data. | ||
If it is needed to use your own certificates, create `che-tls` secret (see `k8s.tlsSecretName` option) with `key.crt` and `tls.crt` fields. In case of self-signed certificate `self-signed-certificate` secret should be created with the public part of CA certificate under `ca.crt` key in secret data. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Here we can add a note, that is is possible to use default certificate of Kubernetes cluster by passing empty string as a value of tlsSecretName
:
spec:
k8s:
tlsSecretName: ''
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: AndrienkoAleksandr, mmorhun The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Signed-off-by: Anatolii Bazko <abazko@redhat.com>
New changes are detected. LGTM label has been removed. |
Signed-off-by: Anatolii Bazko <abazko@redhat.com>
@AndrienkoAleksandr: The following test failed, say
Full PR test history. Your PR dashboard. 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. I understand the commands that are listed here. |
What does this pr do:
Fix outdated info. Add more development info: how to debug che-operator, how to check che-operator compilation, info about CR/CRD and when should be updated Olm bundle, how to add new role/cluster role, how to use chectl to test che-operator and more.
Referenced issue:
eclipse-che/che#18295
Signed-off-by: Oleksandr Andriienko oandriie@redhat.com