I'm pretty new with k8s and k8ssandra project.
I just deployed k8ssandra operator followed https://docs-v2.k8ssandra.io/ V2 version instruction on k8s cluster.
After that, I could not found the reaper or grafana services and pods.
What I expecting is just like what the official site said, they combined reaper and grafana into k8ssandra operator project.
Really need your help if you have any idea about this solution.
[EDITED] I found out from the K8ssandra developers that the example Single-cluster install with helm deploys a minimal cluster with the minimum components configured.
We don't have a nice procedure in the docs for deploying Reaper but you can use the example CRD here to deploy it.
In relation to Grafana, they've decided not to deploy a Grafana pod with K8ssandra because the feedback that they got was that most organisations already have their own Prometheus/Grafana infrastructure. Follow the instructions here to deploy the Prometheus operator and Grafana.
Apologies that this isn't clear with our docs which are still being updated with details of the new K8ssandra operator. Cheers!
Related
I am fiddling around with Kubernetes on a small managed cluster within AKS.
It looks like I'm ready to go with deploying as my node pools are already provisioned and bootstrapped (or that's what it looks like) upon setup.
Am I missing something here?
Do I really need kubeadm on a managed cloud cluster?
You DO NOT need kubeadm tool when using Azure AKS / AWS EKS / Google GKE managed Kubernetes clusters.
kubeadm is used to create a self-managed Kubernetes cluster.
You can use the kubeadm tool to create and manage Kubernetes clusters. It performs the actions necessary to get a minimum viable, secure cluster up and running in a user friendly way.
So for background, I am trying to deploy a containerized webapp inside a kubernetes cluster, which is secured and monitored by istio ft kiali. As I do not want to configure everything by hand I am using Terraform to deploy and update any configurations inside the cluster (like deploying services and pods).
They benefit is that Terraform automatically configures the services needed to expose the apps which safes a lot of hassle, especially because this is a pilot project for a larger deployment of that sort.
The problem now is that Terraform does not include Istio as a provider. There is a way to install and configure it by writing the config inside Terraform, which uses Helm, which configures Istio, but Helm is using the Helm Tiller, a permission-elevated pod which executes given tasks. I do not want a permission-elevated pod inside my cluster due to large scale security concerns.
The question now is: Has someone tried or managed to successfully configure the Istio Services like a VirtualService to expose the webapp through the istio-ingressgateway with a Terraform config file? I googled it but there is little to be seen for the combination of those two.
Terraform now has an official Helm provider https://registry.terraform.io/providers/hashicorp/helm/latest/docs
You can use that provider and install Istio with helm https://istio.io/latest/docs/setup/install/helm/
You can use Kubernetes provider to configure Istio objects.
Refer https://registry.terraform.io/providers/hashicorp/kubernetes/latest/docs and https://www.hashicorp.com/blog/deploy-any-resource-with-the-new-kubernetes-provider-for-hashicorp-terraform
PS: Doing it via Pulumi might be easier checkout https://www.pulumi.com/docs/get-started/kubernetes/
I am trying to use Terraform to create a Service fabric cluster in Azure.
I have created configurations for the follwoing resources using a template provided by Tvo https://github.com/TrevorVonSeggern/ServiceFabric_Terraform
This will create the reasorces in Azure however the SFC just sits on "Deploying" and the Nodes themselves never display.
There seems to be a distinct lack of configuration resources for creating a Service fabric cluster using Terraform and HashiCorp's documentation on this resource example is not as in depth as for other resources.
Provisioning with Powershell is easier as more resources to guide.
If anyone has any working examples please can you share them?
Thanks
I have managed to deploy this successfully by deploying and then going through the extensions in the ARM template. Then adding (in JSON string) in the Terraform config for VMSS
Could not find anywhere in the Terraform documentation on this resource to assist with this.
I have a requirement to use Docker containers in PCF deployed in Azure.
And now we want to use kubernetes as container orchestration.
Does kubernetes can be used here ?
Or PCF will take care of the container orchasteration ?
Which one would be the better approach here ?
PKS Is Pivotal's answer to running kubernetes in PCF (regardless of IaaS)
Pivotal Cloud Foundry (PCF) is a sophisticated answer from Microsoft to current cloud expectations. PCF offers the best platform to run Microsoft based technology like .NET, and smoothly supports enterprise Java application. You can run Kubernetes there with fine results, but to achieve comfortable orchestration and management of containers I suggest reading about GKE or setting up your own Kubernetes cluster using kubespray utility.
I am planning to deploy a production deployment with 'Kubernetes + CoreOS' in Microsoft. And planning to run couple of micro services in the cluster. My plan is to have 5 nodes, I will have 5/6 pods to run each will have 3-5 instances. I was following the official documentation of Kubernetes, I found https://github.com/kubernetes/kubernetes/blob/release-1.0/docs/getting-started-guides/coreos/azure/README.md is really helpful, the script works awesome. But I don't think that its production ready for my use case , as
the deployed VMs are not assigned to Availability Sets
Not able to specify an existing Virtual Network, Resources, location etc.
I am a newbie in this field. Can someone help me out to let me know what all steps to be taken to make this a real production environment ?
the deployed VMs are not assigned to Availability Sets
It is true indeed, as an author and maintainer of the guide, I will welcome a pull-request to enable this, which should be quite easy and probably similar how affinity groups are currently handled.
Not able to specify an existing Virtual Network, Resources, location etc.
This is a very good point, however it's probably best to refactor current ad-hoc JavaScript wrapping to something more streamlined with Azure Resource Manager, which hasn't been generally available at the time I implemented that integration.