Skip to content

Commit

Permalink
Refactor 1
Browse files Browse the repository at this point in the history
  • Loading branch information
bartam1 committed Jul 28, 2022
1 parent 9562310 commit 36415f0
Show file tree
Hide file tree
Showing 3 changed files with 26 additions and 17 deletions.
7 changes: 4 additions & 3 deletions api/v1beta1/kafkacluster_types.go
Original file line number Diff line number Diff line change
Expand Up @@ -92,7 +92,7 @@ type KafkaClusterSpec struct {
// to communicate on SSL with that internal listener which is used for interbroker communication.
// The client certificate must share the same chain of trust as the server certificate used by the corresponding internal listener.
// The secret must contain the keystore, truststore jks files and the password for them in base64 encoded format and
// the tls certificate, tls private key, CA certificate in PEM and base64 encoded format
// the tls certificate, tls private key, CA certificate in PEM format with base64 encoded
// under the keystore.jks, truststore.jks, password, tls.crt, tls.key, and ca.crt data fields.
ClientSSLCertSecret *corev1.LocalObjectReference `json:"clientSSLCertSecret,omitempty"`
}
Expand Down Expand Up @@ -511,8 +511,9 @@ type CommonListenerSpec struct {
// +kubebuilder:validation:Enum=ssl;plaintext;sasl_ssl;sasl_plaintext
Type SecurityProtocol `json:"type"`
// ServerSSLCertSecret is a reference to the Kubernetes secret that contains the server certificate for the listener to be used for SSL communication.
// The secret must contain the keystore, truststore jks files and the password for them in base64 encoded format and the tls certificate in PEM and base64 encoded format
// under the keystore.jks, truststore.jks, password data fields.
// The secret must contain the keystore, truststore jks files and the password for them in base64 encoded format under the keystore.jks, truststore.jks, password data fields.
// When the listener is used for inner broker or controller communication the tls certificate is
// also needed in PEM format with base64 encoding under the tls.crt data field.
// If this field is omitted koperator will auto-create a self-signed server certificate using the configuration provided in 'sslSecrets' field.
ServerSSLCertSecret *corev1.LocalObjectReference `json:"serverSSLCertSecret,omitempty"`
// SSLClientAuth specifies whether client authentication is required, requested, or not required.
Expand Down
18 changes: 11 additions & 7 deletions charts/kafka-operator/templates/crds.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -12260,7 +12260,7 @@ spec:
the corresponding internal listener. The secret must contain the
keystore, truststore jks files and the password for them in base64
encoded format and the tls certificate, tls private key, CA certificate
in PEM and base64 encoded format under the keystore.jks, truststore.jks,
in PEM format with base64 encoded under the keystore.jks, truststore.jks,
password, tls.crt, tls.key, and ca.crt data fields.
properties:
name:
Expand Down Expand Up @@ -19297,9 +19297,11 @@ spec:
secret that contains the server certificate for the listener
to be used for SSL communication. The secret must contain
the keystore, truststore jks files and the password for
them in base64 encoded format and the tls certificate
in PEM and base64 encoded format under the keystore.jks,
truststore.jks, password data fields. If this field is
them in base64 encoded format under the keystore.jks,
truststore.jks, password data fields. When the listener
is used for inner broker or controller communication the
tls certificate is also needed in PEM format with base64
encoding under the tls.crt data field. If this field is
omitted koperator will auto-create a self-signed server
certificate using the configuration provided in 'sslSecrets'
field.
Expand Down Expand Up @@ -19364,9 +19366,11 @@ spec:
secret that contains the server certificate for the listener
to be used for SSL communication. The secret must contain
the keystore, truststore jks files and the password for
them in base64 encoded format and the tls certificate
in PEM and base64 encoded format under the keystore.jks,
truststore.jks, password data fields. If this field is
them in base64 encoded format under the keystore.jks,
truststore.jks, password data fields. When the listener
is used for inner broker or controller communication the
tls certificate is also needed in PEM format with base64
encoding under the tls.crt data field. If this field is
omitted koperator will auto-create a self-signed server
certificate using the configuration provided in 'sslSecrets'
field.
Expand Down
18 changes: 11 additions & 7 deletions config/base/crds/kafka.banzaicloud.io_kafkaclusters.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -12259,7 +12259,7 @@ spec:
the corresponding internal listener. The secret must contain the
keystore, truststore jks files and the password for them in base64
encoded format and the tls certificate, tls private key, CA certificate
in PEM and base64 encoded format under the keystore.jks, truststore.jks,
in PEM format with base64 encoded under the keystore.jks, truststore.jks,
password, tls.crt, tls.key, and ca.crt data fields.
properties:
name:
Expand Down Expand Up @@ -19296,9 +19296,11 @@ spec:
secret that contains the server certificate for the listener
to be used for SSL communication. The secret must contain
the keystore, truststore jks files and the password for
them in base64 encoded format and the tls certificate
in PEM and base64 encoded format under the keystore.jks,
truststore.jks, password data fields. If this field is
them in base64 encoded format under the keystore.jks,
truststore.jks, password data fields. When the listener
is used for inner broker or controller communication the
tls certificate is also needed in PEM format with base64
encoding under the tls.crt data field. If this field is
omitted koperator will auto-create a self-signed server
certificate using the configuration provided in 'sslSecrets'
field.
Expand Down Expand Up @@ -19363,9 +19365,11 @@ spec:
secret that contains the server certificate for the listener
to be used for SSL communication. The secret must contain
the keystore, truststore jks files and the password for
them in base64 encoded format and the tls certificate
in PEM and base64 encoded format under the keystore.jks,
truststore.jks, password data fields. If this field is
them in base64 encoded format under the keystore.jks,
truststore.jks, password data fields. When the listener
is used for inner broker or controller communication the
tls certificate is also needed in PEM format with base64
encoding under the tls.crt data field. If this field is
omitted koperator will auto-create a self-signed server
certificate using the configuration provided in 'sslSecrets'
field.
Expand Down

0 comments on commit 36415f0

Please sign in to comment.