k8s.microcks-default.yml Maven / Gradle / Ivy
The newest version!
apiVersion: microcks.io/v1alpha1
kind: Microcks
metadata:
name: microcks
spec:
version: latest
microcks:
image:
registry: quay.io
repository: microcks/microcks
replicas: 1
ingress:
generateCert: true
resources:
requests:
cpu: 200m
memory: 512Mi
limits:
memory: 512Mi
env:
- name: SERVICES_UPDATE_INTERVAL
value: 0 0 0/2 * * *
openshift:
route:
enabled: true
tlsTermination: edge
logLevel: INFO
mockInvocationStats: true
postman:
image:
registry: quay.io
repository: microcks/microcks-postman-runtime
replicas: 1
resources:
requests:
memory: 256Mi
limits:
memory: 256Mi
keycloak:
install: true
ingress:
generateCert: true
volumeSize: 1Gi
resources:
requests:
cpu: 400m
memory: 400Mi
openshift:
route:
enabled: true
type: edge
realm: microcks
serviceAccount: microcks-serviceaccount
serviceAccountCredentials: ab54d329-e435-41ae-a900-ec6b3fe15c54
mongodb:
install: true
persistent: true
volumeSize: 2Gi
resources:
requests:
cpu: 250m
memory: 512Mi
limits:
memory: 512Mi
features:
async:
enabled: false
image:
registry: quay.io
repository: microcks/microcks-async-minion
defaultBinding: KAFKA
defaultFrequency: 10
defaultAvroEncoding: RAW
kafka:
install: true
ingressClassName: nginx
resources:
#requests:
#cpu: 100m
#memory: 256Mi
limits:
#cpu: 500m
memory: 800Mi
zkResources:
#requests:
#cpu: 100m
#memory: 256Mi
limits:
#cpu: 500m
memory: 800Mi
schemaRegistry:
confluent: true
username: ""
credentialsSource: USER_INFO
authentication:
# If not 'NONE', we support 'SSL' for mutual TLS and 'SASL_SSL' for SASL over TLS.
type: NONE
# For TLS transport, you'll always need a truststore to hold your cluster certificate.
# You have to setup a truststore type and a secret reference for retrieving content and password.
truststoreType: PKCS12
#truststore_secret_ref:
#name: kafka-cluster-ca-cert
#store_key: ca.p12
#password_key: ca.password
# For mutual TLS authentication, you'll also need a keystore to hold your user private key.
# You have to setup a keystore type and a secret reference for retrieving content and password.
keystoreType: PKCS12
keystoreSecretRef:
name: mtls-user
store_key: user.p12
password_key: user.password
# For SASL authentication, you'll have to specify an additional authentication mechanism
# as well as a JAAS configuration line with login module, username and password.
#sasl_mechanism: SCRAM-SHA-512
#sasl_jaas_config: org.apache.kafka.common.security.scram.ScramLoginModule required username="scram-user" password="tDtDCT3pYKE5";
sqs:
#region: eu-west-3
credentialsType: env-variable
#credentialsType: profile
credentialsProfile: microcks-sqs-admin
credentialsSecretRef:
#name: aws-credentials
accessKeyIdKey: access_key_id
secretAccessKeyKey: secret_access_key
#sessionTokenKey: session_token
#fileKey: aws.profile
sns:
#region: eu-west-3
credentialsType: env-variable
#credentialsType: profile
credentialsProfile: microcks-sns-admin
credentialsSecretRef:
#name: aws-credentials
accessKeyIdKey: access_key_id
secretAccessKeyKey: secret_access_key
#sessionTokenKey: session_token
#fileKey: aws.profile
repositoryFilter:
enabled: false
labelKey: domain
labelLabel: Domain
labelList: domain,status
repositoryTenancy:
enabled: false
artifactImportAllowedRoles: admin,manager,manager-any
microcksHub:
enabled: true
allowedRoles: admin,manager,manager-any
aiCopilot:
enabled: false
implementation: openai
openai:
apiKey: sk-my-openai-api-token
timeout: 20
© 2015 - 2025 Weber Informatics LLC | Privacy Policy