Moreover, whenver I enable automigrate the other p...
# talk-kratos
f
Moreover, whenver I enable automigrate the other pods are not created, is this a feature?
s
@worried-kitchen-94392 might be able to answer this, he is the helmmeister 😉
f
+ I have tried to disable the automigration but the pod is re-created yet. Hence, I have deleted all the kratos stuffs from kubernetes and then re-installed the helm with automigrate false.
Moreover, Even though all the pods are marked as green, all the services are not working. E.g. the administration panel is not reachable as the kratos endpoint, i have nodeport as type
For sake of clarify this is my configuration:
deployment:
extraVolumes:
- name: kratos-schema-volume
configMap:
name: kratos-schema
extraVolumeMounts:
- name: kratos-schema-volume
mountPath: /etc/config/kratos
service:
admin:
enabled: true
type: NodePort
public:
enabled: true
type: NodePort
kratos:
autoMigrate: false
config:
identity:
default_schema_url: <file://etc/config/kratos/user.schema.json>
schemas:
- id: user
url: <file://etc/config/kratos/user.schema.json>
dsn: <mysql://root:root@tcp>(mariadb.kratos:3306)/users
secrets:
session:
- 59745DE1FBA793E7A466384D94BD8
log:
level: trace
courier:
smtp:
connection_uri: <smtps://user:pass@smtp.gmail.com:465/?skip_ssl_verify=true>
from_name: MyApp
from_address: <mailto:no-reply@myapp.com|no-reply@myapp.com>
selfservice:
default_browser_return_url: <https://127.0.0.1/dashboard>
methods:
password:
enabled: true
It looks as a basic scenario to me, in my user.schema i have only email and name as fields.
l
I'm interested too
@worried-kitchen-94392
this solved the problem
f
Thanks, it works also for me