Overview
With Kubernetes 1.16 available for a while and starting to slowly roll out across many managed Kubernetes platforms, you might have heard about API deprecations. While fairly simple to deal with, this change might seriously disrupt your services if left unattended.
As Kubernetes feature set evolves, APIs have to evolve too in order to support this change. There are rules in place that aim to guarantee compatibility and stability, and also it does not happen with every release, but eventually, you will have to use the new API version and format as the old one will not be supported anymore.
You can manually go through all your manifests, but that can be fairly time-consuming, it is easy to miss some and might be highly unpractical if you have multiple teams deploying to the cluster, or simply do not have all the current manifest at one place. And this is where Kube No Trouble aka kubent comes to help.
You can easily configure this tool from AWS.
This product collects company name and email address. This information is sent to and stored by the Matoffo. This information will only be used to contact the buyer in regards to the
Highlights
- Kubent will connect to your cluster, retrieve all resources that might be affected, scan, and print summary of those that are.
Details
Features and programs
Financing for AWS Marketplace purchases
Quick Launch
Pricing
Vendor refund policy
Free of charge, no refund required.
Legal
Vendor terms and conditions
Content disclaimer
Delivery details
New delivery option 1
- Amazon EKS
Helm chart
Helm charts are Kubernetes YAML manifests combined into a single package that can be installed on Kubernetes clusters. The containerized application is deployed on a cluster by running a single Helm install command to install the seller-provided Helm chart.
Version release notes
This tool will be able to detect deprecated APIs depending on how you deploy your resources, as we need the original manifest to be stored somewhere. In particular following tools are supported:
file - local manifests in YAML or JSON kubectl - uses the kubectl.kubernetes.io/last-applied-configuration annotation Helm v3 - uses Helm manifests stored as Secrets or ConfigMaps directly in individual namespaces Additional resources:
Blog post on K8s deprecated APIs and introduction of kubent: Kubernetes: Deprecated APIs aka Introducing Kube-No-Trouble
Additional details
Usage instructions
Step 1: Provision AWS Infrastructure EC2 Instances: Set up EC2 instances for KubeNT components such as agents, collectors, and possibly a dashboard server.
Networking: Ensure proper networking configurations, including security groups, VPC settings, and subnet assignments to allow communication between KubeNT components and your Kubernetes cluster.
Storage (Optional): If necessary, provision storage volumes for data persistence.
Step 2: Prepare Kubernetes Cluster Install kubectl: If you haven't already, install kubectl, the Kubernetes command-line tool, on your local machine.
Configure Access: Set up kubectl to access your Kubernetes cluster. This typically involves obtaining the kubeconfig file from your cluster provider and setting it up locally.
Step 3: Deploy KubeNT Components Deploy Agents: Deploy KubeNT agents as DaemonSets in your Kubernetes cluster. These agents collect network telemetry data.
Deploy Collectors: Deploy KubeNT collectors. These receive data from agents and aggregate it for further analysis.
Deploy Dashboard (Optional): If KubeNT includes a dashboard component, deploy it to visualize telemetry data.
Step 4: Configure KubeNT Components Agent Configuration: Configure KubeNT agents to point to the collectors. This usually involves setting environment variables or configuration files.
Collector Configuration: Configure collectors to receive data from agents and possibly store it or forward it for further processing.
Step 5: Test and Monitor Testing: Verify that KubeNT components are running correctly and communicating with each other.
Monitoring: Set up monitoring and alerting for KubeNT components to ensure their ongoing health and performance.
Step 6: Integration and Customization (Optional) Integration with Other Tools: Integrate KubeNT with other monitoring or analytics tools in your ecosystem for enhanced visibility and analysis.
Customization: Customize KubeNT configurations as per your specific requirements, such as adjusting data retention policies or adding custom dashboards.
Step 7: Documentation and Maintenance Documentation: Document the setup and configurations for future reference and to facilitate knowledge sharing within your team.
Maintenance: Establish a maintenance plan for ongoing updates, upgrades, and troubleshooting of KubeNT components.
Support
Vendor support
Together with Matoffo we offer 24/7 Support: round-the-clock customer support to address any issues or concerns that customers may encounter at any time. Our compnay will provide guidance on best practices to ensure customers are getting the most out of the product and making use of its features effectively. In case of troubleshooting, enabling services, requests of pricing policy, refunds do not hesitate to contact us on contact@matoffo.com , we will provide fast feedback and resolve problems with proper care and handling. For more contacts please check our website:
AWS infrastructure support
AWS Support is a one-on-one, fast-response support channel that is staffed 24x7x365 with experienced and technical support engineers. The service helps customers of all sizes and technical abilities to successfully utilize the products and features provided by Amazon Web Services.
Similar products
