• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

chideat / valkey-operator / 34866477612
36%

Build:
DEFAULT BRANCH: main
Ran 14 Sep 2026 04:09PM UTC
Jobs 1
Files 147
Run time 1min
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

14 Sep 2026 04:06PM UTC coverage: 26.536%. Remained the same
34866477612

push

github

web-flow
test(e2e): cover TLS enabled instances end to end (#126)

Nothing in the suite ever deployed an instance with access.enableTLS, which
is why two separate defects shipped unnoticed:

  - the operator never registered the cert-manager types in its scheme, so it
    could not construct the Certificate such an instance needs and the
    instance stalled in Initializing;
  - the client config used to reach the nodes set InsecureSkipVerify, so the
    CA held in the instance secret was never consulted.

Neither is observable from a non-TLS instance, so the suite stayed green
through both.

These cases deploy a TLS instance of each architecture against a real
cert-manager CA and then assert:

  - the instance reaches Ready, which is what the scheme registration gates;
  - the Certificate is issued and the secret carries a complete chain;
  - a handshake against every node completes with a verified chain, built
    through the operator's own LoadCertConfigFromSecret rather than a copy of
    it, so the helper is what is under test;
  - InsecureSkipVerify is off and a server name is set -- the nodes are
    dialled by IP while the certificate carries DNS names only, so one without
    the other cannot verify;
  - plaintext access is refused, since the server runs with --port 0;
  - the instance stays ready and verifiable after a node restart.

The cases run against one valkey version but both access modes. TLS wiring
does not vary with the valkey version, while ClusterIP and NodePort reach the
nodes through different addresses, which is the axis TLS is sensitive to.
Deploying the full version matrix would add nothing and cost an instance
rollout per combination.

cert-manager ships no issuer, so the cases bootstrap a self-signed issuer, a
CA certificate from it, and a CA ClusterIssuer -- a real chain to a separate
root, so chain verification means something. The e2e client needs the
cert-manager types in its scheme for the same reason the operator does.

5516 of 20787 relevant lines covered (26.54%)

0.3 hits per line

Jobs
ID Job ID Ran Files Coverage
1 34866477612.1 14 Sep 2026 04:09PM UTC 147
26.54
GitHub Action Run
Source Files on build 34866477612
  • Tree
  • List 147
  • Changed 0
  • Source Changed 0
  • Coverage Changed 0
Coverage ∆ File Lines Relevant Covered Missed Hits/Line
  • Back to Repo
  • f2a8673e on github
  • Prev Build on main (#34821160671)
  • Next Build on main (#34866629600)
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE TRIAL · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc