I went ahead and rebuilt the Hadoop image module in the same style. I
rebased the zookeeper-single and hdfs kustimize implementations onto the
same structure. So, PR’s #118, #119, #120, and #121 are all in this style.
I don’t have a place for running integration tests, but unit tests are now
Sorry that I’m on vacation and will be back online after 06/06 , but thanks
for putting the PR out and I believe someone on our side will review it . (
or when I come back I will review them)
-Stephen
On Mon, May 22, 2023 at 6:08 PM Nick Dimiduk wrote:
> Heya team,
>
> I have rebuilt one of
Heya team,
I have rebuilt one of the early PRs so that the docker image build pieces
are integrated with the maven build. If this is acceptable to the
reviewers, I'll go forward with integrating the other images and
kustomize/kuttl tests in the same way.
Please take a look.
Thanks,
Nick
Heya team,
I have created individual pull-requests for each of the major functional
pieces outlined in the initial branch. These await review.
I've now started working integrating the test harness into the maven build.
After a brief detour for a Yetus plugin, I'm now looking instead at maven
Heya team,
I've created a feature ticket [0] from which this contribution can hang.
I've created an associated release version [1] and feature branch [2]
against which we can target PRs while things take shape. I've published my
initial extraction of this feature as a whole for your review [3] --
We have implemented deployments secured with Kerberos. It is no less painful on
kubernetes.
Our team at $dayjob does not operate or manage the Kerberos service itself, I
suppose that shifts the pain. I could not give advice on how best to operate
krb on k8s beyond “don’t do it”.
Consider an
Indeed, as with Andrew's comments, we have encountered several "usual
suspects" in terms of network issues. Many of our fixes have either landed
upstream or are waiting in PRs that need to be merged. I'm sure there are
lingering issues, and I'm sure that new issues will arise as we run on more
We have also completed a migration to kubernetes (more specifically, EKS)
at $dayjob. Our basic deployment stack is helm, terraform, and spinnaker,
so we took a different approach in implementation. I think we would be
happy to review and offer advice/opinion/suggestion on points of
commonality,
Hi Nick,
Other than your concerns on the Apache infrastructure, our end are
interests and discussed internally about how HBase could be deployed in
K8s, but would it be possible to share any architecture diagram or design
documentation?
Although moving ZK, HDFS, HBase sounds like as simple as
Thank you both for your comments. I'm happy to hear that there is some
interest in this pursuit.
Before we get too deep into details of the implementation, I'm concerned
that we have support from ASF Infra. Can we install KIND or MiniKube on
Jenkins worker hosts? Can we get a full cluster
Hi Nick,
I do not mean to derail your mail so I'll keep mine short: Yes, I
think testing & infrastructure on Kubernetes would be worthwhile and I
thank you for the offer.
We're happy to take a look and would try to review any incoming
contributions depending on how large/digestable they are :)
Hi Nick,
I agree with your thought that there is an increasing reliance on
kubernetes, more so for complex workloads like hbase deployments because of
unavailability of reliable automation frameworks outside of k8s.
But I have a slightly different view in terms of how to achieve it. When I
was
Heya team,
Over here at $dayjob, we have an increasing reliance on Kubernetes for
both development and production workloads. Our tools are maturing and
we're hoping that they might be of interest to the wider community.
I'd like to see if there's community interest in receiving some/any of
them
13 matches
Mail list logo
