Mikołaj Walczak
Mikołaj Walczak
CircleCI is used only for linter checks, so we know if the build is broken or only linting did not pass. You should modify the Travis configuration file https://github.com/facebookincubator/fbender/blob/master/.travis.yml.
I think build matrices feature of Travis-CI may be of help (https://docs.travis-ci.com/user/build-matrix/).
@advancedwebdeveloper since the project has been migrated from TravisCI to Github Actions maybe it will be easier to do it now. Simply creating a new action to run.
I can prepare a PR if it is agreed on, but it will most likely break the backwards compatibility.
@cgordon since you've been working on a new version could you consider allowing user to provide their own time measure checkpoints (optional)? Setup before sending a request might take a...
@cgordon yes, that seems like a good solution
It seems like the user doesn't have permission to create resources at the global scope level. You can create an RBAC rule and give permissions to the user `"system:serviceaccount:mysql-operator:default"` (using...
I just saw that you're running it in a custom namespace. I've created a PR which will allow to specify namespace to register CRDs in. https://github.com/grtl/mysql-operator/pull/127 - I will merge...
> @earlgreyz thank you so much, you are awesome. I think it should have ability to run in a separated namespace. Already merged, let me know if it works for...
@chenmin1992 did you run the deployment with the `-namespace mysql-operator` flag? You might still need to create RBAC rule to allow user for modifying the `mysql-operator` namespace.