digitalshuffler
commented
2 years ago Hello, we got any revision?
We need some help whit this issue.
Open digitalshuffler opened 2 years ago
digitalshuffler
commented
2 years ago Hello, we got any revision?
We need some help whit this issue.
banzo
commented
2 years ago @digitalshuffler can you reproduce the problem with the new release?
anshurajkaushik
commented
2 years ago @banzo : i am facing the same problem with the latest release ,below is my values.yaml
---
# Number of nifi nodes
replicaCount: 3
## Set default image, imageTag, and imagePullPolicy.
## ref: https://hub.docker.com/r/apache/nifi/
##
image:
repository: apache/nifi
tag: "1.14.0"
pullPolicy: "IfNotPresent"
## Optionally specify an imagePullSecret.
## Secret must be manually created in the namespace.
## ref: https://kubernetes.io/docs/tasks/configure-pod-container/pull-image-private-registry/
##
# pullSecret: myRegistrKeySecretName
securityContext:
runAsUser: 1000
fsGroup: 1000
## @param useHostNetwork - boolean - optional
## Bind ports on the hostNetwork. Useful for CNI networking where hostPort might
## not be supported. The ports need to be available on all hosts. It can be
## used for custom metrics instead of a service endpoint.
##
## WARNING: Make sure that hosts using this are properly firewalled otherwise
## metrics and traces are accepted from any host able to connect to this host.
#
sts:
# Parallel podManagementPolicy for faster bootstrap and teardown. Default is OrderedReady.
podManagementPolicy: Parallel
AntiAffinity: soft
useHostNetwork: null
hostPort: null
pod:
annotations:
security.alpha.kubernetes.io/sysctls: net.ipv4.ip_local_port_range=10000 65000
#prometheus.io/scrape: "true"
serviceAccount:
create: false
#name: nifi
annotations: {}
hostAliases: []
# - ip: "1.2.3.4"
# hostnames:
# - example.com
# - example
## Useful if using any custom secrets
## Pass in some secrets to use (if required)
# secrets:
# - name: myNifiSecret
# keys:
# - key1
# - key2
# mountPath: /opt/nifi/secret
## Useful if using any custom configmaps
## Pass in some configmaps to use (if required)
# configmaps:
# - name: myNifiConf
# keys:
# - myconf.conf
# mountPath: /opt/nifi/custom-config
properties:
# use externalSecure for when inbound SSL is provided by nginx-ingress or other external mechanism
sensitiveKey: changeMenifipoc # Must to have minimal 12 length key
algorithm: NIFI_PBKDF2_AES_GCM_256
externalSecure: true
isNode: true
httpsPort: 8443
webProxyHost: # <clusterIP>:<NodePort> (If Nifi service is NodePort or LoadBalancer)
clusterPort: 6007
provenanceStorage: "8 GB"
siteToSite:
port: 10000
# use properties.safetyValve to pass explicit 'key: value' pairs that overwrite other configuration
safetyValve:
#nifi.variable.registry.properties: "${NIFI_HOME}/example1.properties, ${NIFI_HOME}/example2.properties"
nifi.web.http.network.interface.default: eth0
# listen to loopback interface so "kubectl port-forward ..." works
nifi.web.http.network.interface.lo: lo
## Include aditional processors
# customLibPath: "/opt/configuration_resources/custom_lib"
## Include additional libraries in the Nifi containers by using the postStart handler
## ref: https://kubernetes.io/docs/tasks/configure-pod-container/attach-handler-lifecycle-event/
# postStart: /opt/nifi/psql; wget -P /opt/nifi/psql https://jdbc.postgresql.org/download/postgresql-42.2.6.jar
# Nifi User Authentication
auth:
admin: CN=admin, OU=NIFI
SSL:
keystorePasswd: changeMe
truststorePasswd: changeMe
# Automaticaly disabled if OIDC or LDAP enabled
singleUser:
username: username
password: changemechangeme # Must to have at least 12 characters
ldap:
enabled: false
host:
searchBase: CN=Users,DC=ldap,DC=example,DC=be
admin: cn=admin,dc=ldap,dc=example,dc=be
pass: ChangeMe
searchFilter: (objectClass=*)
userIdentityAttribute: cn
authStrategy: SIMPLE # How the connection to the LDAP server is authenticated. Possible values are ANONYMOUS, SIMPLE, LDAPS, or START_TLS.
identityStrategy: USE_DN
authExpiration: 12 hours
oidc:
enabled: true
discoveryUrl: https://login.microsoftonline.com/<tenant_id>/v2.0/.well-known/openid-configuration
clientId: *******
clientSecret: ****************
claimIdentifyingUser: preferred_username
## Request additional scopes, for example profile
additionalScopes:
openldap:
enabled: false
persistence:
enabled: true
env:
LDAP_ORGANISATION: # name of your organization e.g. "Example"
LDAP_DOMAIN: # your domain e.g. "ldap.example.be"
LDAP_BACKEND: "hdb"
LDAP_TLS: "true"
LDAP_TLS_ENFORCE: "false"
LDAP_REMOVE_CONFIG_AFTER_SETUP: "false"
adminPassword: #ChengeMe
configPassword: #ChangeMe
customLdifFiles:
1-default-users.ldif: |-
# You can find an example ldif file at https://github.com/cetic/fadi/blob/master/examples/basic/example.ldif
## Expose the nifi service to be accessed from outside the cluster (LoadBalancer service).
## or access it from within the cluster (ClusterIP service). Set the service type and the port to serve it.
## ref: http://kubernetes.io/docs/user-guide/services/
##
# headless service
headless:
type: ClusterIP
annotations:
service.alpha.kubernetes.io/tolerate-unready-endpoints: "true"
# ui service
service:
type: ClusterIP
httpsPort: 8443
# nodePort: 30236
annotations: {}
# loadBalancerIP:
## Load Balancer sources
## https://kubernetes.io/docs/tasks/access-application-cluster/configure-cloud-provider-firewall/#restrict-access-for-loadbalancer-service
##
# loadBalancerSourceRanges:
# - 10.10.10.0/24
## OIDC authentication requires "sticky" session on the LoadBalancer for JWT to work properly...but AWS doesn't like it on creation
# sessionAffinity: ClientIP
# sessionAffinityConfig:
# clientIP:
# timeoutSeconds: 10800
# Enables additional port/ports to nifi service for internal processors
processors:
enabled: false
ports:
- name: processor01
port: 7001
targetPort: 7001
#nodePort: 30701
- name: processor02
port: 7002
targetPort: 7002
#nodePort: 30702
## Configure Ingress based on the documentation here: https://kubernetes.io/docs/concepts/services-networking/ingress/
##
ingress:
enabled: true
annotations:
kubernetes.io/ingress.class: nginx
ingress.kubernetes.io/ssl-redirect: “true”
nginx.ingress.kubernetes.io/affinity: cookie
kubernetes.io/tls-acme: "true"
nginx.ingress.kubernetes.io/upstream-vhost: "localhost:8443"
nginx.ingress.kubernetes.io/proxy-redirect-from: "https://localhost:8443"
nginx.ingress.kubernetes.io/proxy-redirect-to: "https://****************com"
nginx.ingress.kubernetes.io/backend-protocol: HTTPS
# nginx.ingress.kubernetes.io/configuration-snippet: |
# proxy_set_header 'X-ProxyContextPath' '/';
# proxy_set_header 'X-ProxyPort' '80';
# proxy_set_header 'X-ProxyScheme' 'http';
# proxy_set_header X-ProxyPort 443;
# proxy_set_header X-ProxiedEntitiesChain "<$ssl_client_s_dn>"
tls:
- hosts:
- *******************.com
secretName: *************-n-tlssecret
hosts:
- ***********com
path: /
# If you want to change the default path, see this issue https://github.com/cetic/helm-nifi/issues/22
# Amount of memory to give the NiFi java heap
jvmMemory: 2g
# Separate image for tailing each log separately and checking zookeeper connectivity
sidecar:
image: busybox
tag: "1.32.0"
imagePullPolicy: "IfNotPresent"
## Enable persistence using Persistent Volume Claims
## ref: http://kubernetes.io/docs/user-guide/persistent-volumes/
##
persistence:
enabled: false
# When creating persistent storage, the NiFi helm chart can either reference an already-defined
# storage class by name, such as "standard" or can define a custom storage class by specifying
# customStorageClass: true and providing the "storageClass", "storageProvisioner" and "storageType".
# For example, to use SSD storage on Google Compute Engine see values-gcp.yaml
#
# To use a storage class that already exists on the Kubernetes cluster, we can simply reference it by name.
# For example:
# storageClass: standard
#
# The default storage class is used if this variable is not set.
accessModes: [ReadWriteOnce]
## Storage Capacities for persistent volumes
configStorage:
size: 100Mi
authconfStorage:
size: 100Mi
# Storage capacity for the 'data' directory, which is used to hold things such as the flow.xml.gz, configuration, state, etc.
dataStorage:
size: 1Gi
# Storage capacity for the FlowFile repository
flowfileRepoStorage:
size: 10Gi
# Storage capacity for the Content repository
contentRepoStorage:
size: 10Gi
# Storage capacity for the Provenance repository. When changing this, one should also change the properties.provenanceStorage value above, also.
provenanceRepoStorage:
size: 10Gi
# Storage capacity for nifi logs
logStorage:
size: 5Gi
## Configure resource requests and limits
## ref: http://kubernetes.io/docs/user-guide/compute-resources/
##
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
logresources:
requests:
cpu: 10m
memory: 10Mi
limits:
cpu: 50m
memory: 50Mi
## Enables setting your own affinity. Mutually exclusive with sts.AntiAffinity
## You need to set the value of sts.AntiAffinity other than "soft" and "hard"
affinity: {}
nodeSelector: {}
tolerations: []
initContainers: {}
# foo-init: # <- will be used as container name
# image: "busybox:1.30.1"
# imagePullPolicy: "IfNotPresent"
# command: ['sh', '-c', 'echo this is an initContainer']
# volumeMounts:
# - mountPath: /tmp/foo
# name: foo
extraVolumeMounts: []
extraVolumes: []
## Extra containers
extraContainers: []
terminationGracePeriodSeconds: 30
## Extra environment variables that will be pass onto deployment pods
env: []
## Extra environment variables from secrets and config maps
envFrom: []
# envFrom:
# - configMapRef:
# name: config-name
# - secretRef:
# name: mysecret
## Openshift support
## Use the following varables in order to enable Route and Security Context Constraint creation
openshift:
scc:
enabled: false
route:
enabled: false
#host: www.test.com
#path: /nifi
# ca server details
# Setting this true would create a nifi-toolkit based ca server
# The ca server will be used to generate self-signed certificates required setting up secured cluster
ca:
## If true, enable the nifi-toolkit certificate authority
enabled: true
persistence:
enabled: true
server: ""
service:
port: 9090
token: sixteenCharacters
admin:
cn: admin
serviceAccount:
create: false
#name: nifi-ca
openshift:
scc:
enabled: false
# ------------------------------------------------------------------------------
# Zookeeper:
# ------------------------------------------------------------------------------
zookeeper:
## If true, install the Zookeeper chart
## ref: https://github.com/bitnami/charts/blob/master/bitnami/zookeeper/values.yaml
enabled: true
## If the Zookeeper Chart is disabled a URL and port are required to connect
url: ""
port: 2181
replicaCount: 3
# ------------------------------------------------------------------------------
# Nifi registry:
# ------------------------------------------------------------------------------
registry:
## If true, install the Nifi registry
enabled: true
url: ""
port: 80
## Add values for the nifi-registry here
## ref: https://github.com/dysnix/charts/blob/master/nifi-registry/values.yaml
# Configure metrics
metrics:
prometheus:
# Enable Prometheus metrics
enabled: false
# Port used to expose Prometheus metrics
port: 9092
serviceMonitor:
# Enable deployment of Prometheus Operator ServiceMonitor resource
enabled: false
# namespace: monitoring
# Additional labels for the ServiceMonitor
labels: {}
I get up nifi now but seems to drop a warn constantly ¿It's something that we should care? seems like failed requests due to certificates
2022-01-10 15:38:25,490 INFO [Heartbeat Monitor Thread-1] o.a.n.c.c.h.AbstractHeartbeatMonitor Finished processing 1 heartbeats in 24201 nanos
2022-01-10 15:38:25,758 WARN [Process Cluster Protocol Request-6] o.a.n.c.p.impl.SocketProtocolListener Failed processing protocol message from nifi-deploy-dev-1.nifi-deploy-dev-headless.lakehouse-nifi.svc.cluster.local due to Received fatal alert: certificate_unknown
2022-01-10 15:38:27,342 INFO [Process Cluster Protocol Request-7] o.a.n.c.p.impl.SocketProtocolListener Finished processing request 6a97c5ed-0000-4f77-a2c6-94fe1da8ec52 (type=HEARTBEAT, length=2933 bytes) from localhost:8443 in 19 millis
2022-01-10 15:38:27,344 INFO [Clustering Tasks Thread-3] o.a.n.c.c.ClusterProtocolHeartbeater Heartbeat created at 2022-01-10 15:38:27,315 and sent to nifi-deploy-dev-0.nifi-deploy-dev-headless.lakehouse-nifi.svc.cluster.local:6007 at 2022-01-10 15:38:27,344; send took 28 millis@anshurajkaushik your issue seems related to oidc configuration, not ldap
anshurajkaushik
commented
2 years ago @digitalshuffler @banzo : ok i get past the initial issues , but still seeing the -nifi.svc.cluster.local due to Received fatal alert: certificate_unknown. issue
@digitalshuffler : are your nodes connected in cluster ?
and also Untrusted proxy CN=localhost.
any suggestions ?
digitalshuffler
commented
2 years ago I found a solution after needing to modify and fix the chart.
There was 2 things: After the new release, nifi goes up with ldap but when activating HA mode, there is no communication between nodes.
This is caused because toolkit is generating a diferent certificate/key for every pod, so a way to solve it is to generate a unique jks shared by a persistent storage.
Also, the FQDN generated to be in HA mode with HTTPS should be changed to use the entire pod FQDN.
I attach the modified code, casue i can't do a pull request or access the repository. You can compare it from release 1.0.4
I attach to a prove to see that nifi in ha mode with ldap is working:
anshurajkaushik
commented
2 years ago @digitalshuffler : can you attach your values.yaml also , i am still seeing Untrusted proxy CN=localhost .
digitalshuffler
commented
2 years ago @anshurajkaushik Make sure that your tls-toolkit is generating this way and your nifi.web.https.host is equal to the pod name:
/opt/nifi/nifi-toolkit-current/bin/tls-toolkit.sh standalone \
-n {{.Release.Name}}-0.{{.Release.Name}}-headless.{{.Release.Namespace}}.svc.cluster.local \
--subjectAlternativeNames 'localhost,{{.Release.Name}}-[0-{{ $replicas }}].{{.Release.Name}}-headless.{{.Release.Namespace}}.svc.cluster.local' \
-C '{{.Values.auth.ldap.admin}}' \
-O -o "${NIFI_HOME}/conf/" \
-P {{.Values.auth.SSL.truststorePasswd}} \
-S {{.Values.auth.SSL.keystorePasswd}} \
--nifiPropertiesFile /opt/nifi/nifi-current/conf/nifi.properties
Describe the bug When trying to deploy nifi with ldap configuration it throws an error saying that the JKS generated by tls-toolkit.sh is not valid and it refuses to start
Version of Helm, Kubernetes and the Nifi chart: kubernetes v1.19.11 helm Nifi Chart version: 1.0.2
What happened: Nifi falls into a crashLoopBack error Attached full stack trace:
What you expected to happen: Nifi starts correctly
How to reproduce it (as minimally and precisely as possible): Attached values.yaml:
values.yaml:
Anything else we need to know:
I think, the problem is around the generation of the keystores in the statefulset.yaml template wich executes a certain command when auth.ldap is enabled.
No errors where found when nifi starts withouth configuring ldap.