Skip to content
A Kubernetes Operator for Percona Server for MongoDB
Branch: master
Clone or download
Latest commit d45914d Apr 24, 2019
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
build fix image building Apr 22, 2019
clientcmd Add exec package and server version denifing Jan 14, 2019
cmd/manager Add auto ssl Apr 24, 2019
deploy Small changes Apr 24, 2019
e2e-tests fix image building Apr 22, 2019
pkg fix keyfile secret name Apr 24, 2019
vendor Add vendor Apr 24, 2019
version Detect openshift 4.0+ clusters Mar 14, 2019
.client-secret.json.enc
.cloud-secret.yml.enc fix travis Mar 9, 2019
.gitignore Add internal secret name Apr 24, 2019
.travis.yml add storage test for travis Mar 14, 2019
Gopkg.lock Add auto ssl Apr 24, 2019
Gopkg.toml Add auto ssl Apr 24, 2019
LICENSE License Mar 18, 2019
README.md move repository to percona org on github.com Mar 9, 2019

README.md

Percona Server for MongoDB Operator

Build Status Go Report Card

A Kubernetes operator for Percona Server for MongoDB based on the Operator SDK.

Documentation

See the Official Documentation for more information.

Official Documentation

DISCLAIMER

This code is incomplete, expect major issues and changes until this repo has stabilised!

Submitting Bug Reports

If you find a bug in Percona Docker Images or in one of the related projects, please submit a report to that project's JIRA issue tracker.

Your first step should be search for a similar report in the existing set of open tickets. If someone else has already reported your problem, upvote that report to increase its visibility.

If there is no existing report, submit a report following these steps:

  1. Sign in to Percona JIRA. You will need to create an account if you do not have one.
  2. Go to the Create Issue screen and select the relevant project.
  3. Fill in the fields of Summary, Description, Steps To Reproduce, and Affects Version to the best you can. If the bug corresponds to a crash, attach the stack trace from the logs.

An excellent resource is Elika Etemad's article on filing good bug reports..

As a general rule of thumb, please try to create bug reports that are:

  • Reproducible. Include steps to reproduce the problem.
  • Specific. Include as much detail as possible: which version, what environment, etc.
  • Unique. Do not duplicate existing tickets.
  • Scoped to a Single Bug. One bug per report.
You can’t perform that action at this time.