ndimiduk commented on code in PR #3: URL: https://github.com/apache/hbase-kustomize/pull/3#discussion_r1233884551
########## dockerfiles/kuttl/README.md: ########## @@ -0,0 +1,71 @@ +<!-- + Licensed to the Apache Software Foundation (ASF) under one + or more contributor license agreements. See the NOTICE file + distributed with this work for additional information + regarding copyright ownership. The ASF licenses this file + to you under the Apache License, Version 2.0 (the + "License"); you may not use this file except in compliance + with the License. You may obtain a copy of the License at + + http://www.apache.org/licenses/LICENSE-2.0 + + Unless required by applicable law or agreed to in writing, software + distributed under the License is distributed on an "AS IS" BASIS, + WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. + See the License for the specific language governing permissions and + limitations under the License. +--> + +# dockerfiles/kuttl + +This directory builds a docker image containing everything required to run `kubectl-kuttl`. It +includes all the dependencies to run in "mocked control plane" mode as well as targeting a full +cluster. This image is used as the basis for both dev and test environments. + Review Comment: That way that I've used it thus far is as a developer and testing tool for working on this codebase. If someone wants to make use of the hbase-kustomize tools in their environment, they very likely already have kubectl installed and I doubt they have a need to kuttl. I suppose they could use this image to run tests over their own code, but the goal of this image is for self-support, not for user support. Maybe this would be more clear if I instead tied this into the Dockerfile we use for Yetus builds? But then, I don't think that Yetus allows for build arguments over the image it creates for itself in docker mode... -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
