Details
-
Page
-
Resolution: Fixed
-
Major
-
None
-
None
-
1
Description
We have the following section in our doc:
spec.networking.exposedFeatures
|
This field specified a list of per-pod features to expose on the cluster network (as opposed to the pod network). These define sets of ports which are required to support the specified features. The supported values are as follows:
|
|
|
admin
|
Exposes the admin API and UI
|
|
|
xdcr
|
Exposes the ports necessary to support XDCR via L3 connectivity at the cluster network layer.
|
|
|
client
|
Exposes all client services. These include data, views, query, full text search, analytics.
|
|
|
Field rules: The exposedFeatures list is optional, no feature sets are exposed to the cluster network if unset.
|
But we don't show the example of this in the config, namely
spec:
|
networking:
|
exposeAdminConsole: true |
adminConsoleServiceTemplate:
|
metadata:
|
labels:
|
key: value
|
spec:
|
type: LoadBalancer
|
adminConsoleServices: # DEPRECATED
|
- data
|
adminConsoleServiceType: LoadBalancer # DEPRECATED
|
exposedFeatureServiceTemplate:
|
metadata:
|
labels:
|
key: value
|
spec:
|
type: LoadBalancer
|
exposedFeatureServiceType: LoadBalancer # DEPRECATED
|
exposedFeatureTrafficPolicy: Local # DEPRECATED
|
serviceAnnotations: # DEPRECATED
|
my-annotation: my-value
|
loadBalancerSourceRanges: # DEPRECATED
|
- "10.0.0.0/8" |
networkPlatform: Istio
|
dns:
|
domain: couchbase-0.us-east-1.example.com |
tls:
|
static: |
serverSecret: couchbase-server-tls
|
operatorSecret: couchbase-operator-tls
|
clientCertificatePolicy: mandatory
|
clientCertificatePaths:
|
- path: san.email
|
prefix: "" |
delimiter: "@" |
nodeToNodeEncryption: All
|
The previous doc has the following:
networking:
|
exposeAdminConsole: true
|
adminConsoleServices:
|
- data
|
adminConsoleServiceType: LoadBalancer
|
exposedFeatures:
|
- xdcr
|