You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Seems nifi does not trust CA which is let´s encrypt. Isn´t registry compatible with istio? Any idea on how to overcome this issue?
Below my config.
Values.yaml:
# Default values for nifi-registry.
# This is a YAML-formatted file.
# Declare variables to be passed into your templates.
replicaCount: 1
image:
repository: apache/nifi-registry
pullPolicy: IfNotPresent
tag: "0.8.0"
initContainers:
git:
image: alpine/git
tag: v2.26.2
alpine:
image: alpine
tag: 3.6
# Additional environment variables to set for the initContainers
extraEnvs: []
# extraEnvs:
# - name: FOO
# value: bar
imagePullSecrets: []
nameOverride: ""
fullnameOverride: ""
serviceAccount:
# Specifies whether a service account should be created
create: true
# Annotations to add to the service account
annotations: {}
# The name of the service account to use.
# If not set and create is true, a name is generated using the fullname template
name: ""
podAnnotations: {}
#podAnnotations:
# sidecar.istio.io/inject: "false"
podSecurityContext: {}
# fsGroup: 2000
securityContext: {}
# capabilities:
# drop:
# - ALL
# readOnlyRootFilesystem: true
# runAsNonRoot: true
# runAsUser: 1000
service:
type: ClusterIP
port: 18080
ingress:
enabled: false
annotations: {}
# kubernetes.io/ingress.class: nginx
# kubernetes.io/tls-acme: "true"
hosts:
- host: chart-example.local
paths: []
tls: []
# - secretName: chart-example-tls
# hosts:
# - chart-example.local
## Persist data to a persistent volume
persistence:
enabled: true
database:
# storageClass: "-"
accessMode: ReadWriteOnce
size: 1Gi
flowStorage:
# storageClass: "-"
accessMode: ReadWriteOnce
size: 1Gi
#resources: {}
# We usually recommend not to specify default resources and to leave this as a conscious
# choice for the user. This also increases chances charts run on environments with little
# resources, such as Minikube. If you do want to specify resources, uncomment the following
# lines, adjust them as necessary, and remove the curly braces after 'resources:'.
# limits:
# cpu: 100m
# memory: 128Mi
# requests:
# cpu: 100m
# memory: 128Mi
resources:
requests:
memory: 512Mi
cpu: 100m
limits:
memory: 1Gi
cpu: 200m
#Required to use dedicated compute
#nodeSelector: {}
nodeSelector:
function: nifi-network-packet
#Required to use dedicated compute
#tolerations: []
tolerations:
- effect: NoSchedule
key: function
operator: Equal
value: nifi-network-packet
affinity: {}
flowProvider:
git:
enabled: false
url:
remote: origin
user:
password:
# The secret name can be used to supply your own SSH key:
# 1. Generate a SSH key named identity:
# ssh-keygen -q -N "" -f ./identity
# 2. Create a Kubernetes secret:
# kubectl -n nifi-registry create secret generic nifi-registry-git-deploy --from-file=./identity
# 3. Don't check these key files into your Git repository! Once you've created
# the Kubernetes secret, Delete the private key:
# rm ./identity
# 4. Add ./identity.pub as a deployment key with write access in your Git repo
# 5. Set the secret name (default: nifi-registry-git-deploy) below
secretName:
# Global Git configuration See https://git-scm.com/docs/git-config for more details.
config:
enabled: false
secretName: ""
data: ""
# data: |
# [credential "https://github.com"]
# username = foo
postgres:
enabled: false
driverURL: https://jdbc.postgresql.org/download/
fileName: postgresql-42.2.6.jar
driverClass: org.postgresql.Driver
url: jdbc:postgresql://localhost/nifireg
username: nifireg
password: nifireg
# Additional environment variables to set
#extraEnvs: []
#extraEnvs:
#- name: NIFI_REGISTRY_WEB_HTTP_HOST
# value: "0.0.0.0"
ssh:
# Overrides for git over SSH. If you use your own git server, you
# will likely need to provide a host key for it in this field.
known_hosts: ""
config: ""
# specify the config which would go in /home/nifi/.ssh/config file
# for e.g.
# config: |
# Host github.com
# ProxyCommand socat STDIO PROXY:<proxyIP>:%h:%p,proxyport=<proxyPort>,proxyauth=<username:password>
# User git
# Hostname ssh.github.com
# Port 443
# IdentityFile /etc/fluxd/ssh/identity
tests:
images:
busybox:
image: busybox
tag: 1.33.1
Hi
I am using nifi-registry 0.3.5 deployed in k8s with istio enabled and i am able to reach registry UI (after setting hostname to "0.0.0.0").
However, when configuring the registry url (https://nifi-registry.network-packet.staging.xxx.net/nifi-registry) on nifi and then trying to start version control in a PG have the following error:
Seems nifi does not trust CA which is let´s encrypt. Isn´t registry compatible with istio? Any idea on how to overcome this issue?
Below my config.
Values.yaml:
Statefulset.yaml:
virtualservice.yaml:
The text was updated successfully, but these errors were encountered: