mirror of
https://github.com/hanzoai/ingress.git
synced 2026-10-26 02:47:15 +00:00
Everything here is a string a human or a customer could read. Three of them were also stale enough to be wrong against the current runtime: - nomad fixtures tagged `traefik.enable=true` while the provider's default prefix has been `ingress` for some time -- the tags matched nothing. Now `ingress.*`, consistent with nomad_test's own cases. - integration rawdata fixtures expected `"entryPoints": ["traefik"]`, but DefaultInternalEntryPointName is `ingress`. - the digestauth compose fixture carried htdigest hashes computed over realm `traefik`, while auth.defaultRealm is `ingress` -- so those credentials could not have authenticated. Recomputed against the real realm: md5(test:ingress:test) and md5(test2:ingress:test2). Also: the CRD fixture that integration actually applies (its `description:` text reaches customers through `kubectl explain`), the repo hero image, a test comment, and a cert-generation note. The CRD descriptions are set to exactly what the (already clean) Go doc comments generate, so a fixed regeneration is a no-op diff. LLM.md is rewritten to match: the ownership table now records direct requires instead of `replace`, and the "intentionally stays" register is corrected -- the digest-realm entry was stale (that file has used realm `ingresser` for a while), and the entries that genuinely stay are stated with the reason they stay: licence attribution, k3s's `--disable=traefik` flag, upstream Docker Hub image addresses, and one upstream issue URL. Two remaining leaks are tracked rather than papered over: the stale `traefik.io_*.yaml` CRD dumps (blocked on a broken code-gen.sh glob) and `OU=Traefik` in the acme test certificate.
3.6 KiB
3.6 KiB
This is how the certs were created
Password: ingress
# ca1.example.com
# Country Name (2 letter code) [AU]:.
# State or Province Name (full name) [Some-State]:.
# Locality Name (eg, city) []:.
# Organization Name (eg, company) [Internet Widgits Pty Ltd]:.
# Organizational Unit Name (eg, section) []:.
# Common Name (e.g. server FQDN or YOUR name) []:ca1.example.com
# Email Address []:.
openssl req -new -newkey rsa:2048 -x509 -days 3650 -extensions v3_ca -keyout ca1.pem -out ca1.crt
# ca2.example.com
# Country Name (2 letter code) [AU]:.
# State or Province Name (full name) [Some-State]:.
# Locality Name (eg, city) []:.
# Organization Name (eg, company) [Internet Widgits Pty Ltd]:.
# Organizational Unit Name (eg, section) []:.
# Common Name (e.g. server FQDN or YOUR name) []:ca2.example.com
# Email Address []:.
openssl req -new -newkey rsa:2048 -x509 -days 3650 -extensions v3_ca -keyout ca2.pem -out ca2.crt
# ca3.example.com
# Country Name (2 letter code) [AU]:.
# State or Province Name (full name) [Some-State]:.
# Locality Name (eg, city) []:.
# Organization Name (eg, company) [Internet Widgits Pty Ltd]:.
# Organizational Unit Name (eg, section) []:.
# Common Name (e.g. server FQDN or YOUR name) []:ca3.example.com
# Email Address []:.
openssl req -new -newkey rsa:2048 -x509 -days 3650 -extensions v3_ca -keyout ca3.pem -out ca3.crt
openssl rsa -in ca1.pem -out ca1.key
openssl rsa -in ca2.pem -out ca2.key
openssl rsa -in ca3.pem -out ca3.key
cat ca1.crt ca2.crt > ca1and2.crt
rm ca1.pem ca2.pem ca3.pem
openssl genrsa -out client1.key 2048
openssl genrsa -out client2.key 2048
openssl genrsa -out client3.key 2048
# Country Name (2 letter code) [AU]:.
# State or Province Name (full name) [Some-State]:.
# Locality Name (eg, city) []:.
# Organization Name (eg, company) [Internet Widgits Pty Ltd]:.
# Organizational Unit Name (eg, section) []:.
# Common Name (e.g. server FQDN or YOUR name) []:client1.example.com
# Email Address []:.
#
# Please enter the following 'extra' attributes
# to be sent with your certificate request
# A challenge password []:
#
# Issuer
# CN = ca1.example.com
# Subject
# CN = client1.example.com
openssl req -key client1.key -new -out client1.csr
# Country Name (2 letter code) [AU]:.
# State or Province Name (full name) [Some-State]:.
# Locality Name (eg, city) []:.
# Organization Name (eg, company) [Internet Widgits Pty Ltd]:.
# Organizational Unit Name (eg, section) []:.
# Common Name (e.g. server FQDN or YOUR name) []:client2.example.com
# Email Address []:.
#
# Please enter the following 'extra' attributes
# to be sent with your certificate request
# A challenge password []:
#
# Issuer
# CN = ca2.example.com
# Subject
# CN = client2.example.com
openssl req -key client2.key -new -out client2.csr
# Country Name (2 letter code) [AU]:.
# State or Province Name (full name) [Some-State]:.
# Locality Name (eg, city) []:.
# Organization Name (eg, company) [Internet Widgits Pty Ltd]:.
# Organizational Unit Name (eg, section) []:.
# Common Name (e.g. server FQDN or YOUR name) []:client3.example.com
# Email Address []:.
#
# Please enter the following 'extra' attributes
# to be sent with your certificate request
# A challenge password []:
#
# Issuer
# CN = ca3.example.com
# Subject
# CN = client3.example.com
openssl req -key client3.key -new -out client3.csr
openssl x509 -req -days 3650 -in client1.csr -CA ca1.crt -CAkey ca1.key -CAcreateserial -out client1.crt
openssl x509 -req -days 3650 -in client2.csr -CA ca2.crt -CAkey ca2.key -CAcreateserial -out client2.crt
openssl x509 -req -days 3650 -in client3.csr -CA ca3.crt -CAkey ca3.key -CAcreateserial -out client3.crt