Budget: 500 USD Deadline: 5 days
Hello! I can help understand your system and solve problems if possible
🔧 DevOps Specialist for Kubernetes Cluster Audit and Optimization
Task Description:
We are looking for an experienced DevOps engineer for a one-time task - to audit the current Kubernetes cluster, identify errors, weaknesses, and suggest improvements. We need someone who will not "set up from scratch," but quickly understand the current architecture and find where we are making mistakes.
What needs to be done:
Review the current infrastructure (Kubernetes, Helm, CI/CD, monitoring, ingress, etc.)
Find bugs, incorrect configs, security issues, logging, and scaling problems
Provide recommendations for fixes (preferably with prioritization)
Requirements:
Confident knowledge of Kubernetes (and a passion for troubleshooting)
Experience in cluster auditing and optimization,
Ability to work quickly and to the point
Budget: 500 USD Deadline: 5 days
Hello! I can help understand your system and solve problems if possible
Budget: 500 USD Deadline: 5 days
Good afternoon!
There is experience with Kubernetes bare metal and cloud. I can conduct a cluster review.
Budget: 25 USD Deadline: 4 days
Hello,
We are SolidWay company, and we are ready to help with your project involving the audit and optimization of your Kubernetes cluster. Our team has extensive experience in handling similar tasks, including identifying issues and suggesting improvements in Kubernetes environments. We understand the complexities involved and can provide effective solutions tailored to your needs.
We are well-versed in assessing infrastructure components such as Kubernetes, Helm, CI/CD, and monitoring systems. Our approach involves a thorough evaluation of your current setup to pinpoint configuration errors, security vulnerabilities, and scalability challenges, along with prioritized recommendations for enhancements.
We’ll define the timeframe and budget after we discuss the task in more detail. Let's connect to ensure we understand all the specifics so we can proceed effectively.
As part of enhancing the cybersecurity level of our infrastructure, we need to abandon the practice of storing "eternal" and static API keys, passwords, and integration tokens in the configuration files (.env, appsettings.json, config.yaml) of our microservices. Business Goal: Create a single secure storage point for confidential data (secrets) with a mechanism for their automatic updating (rotation) in external systems on a schedule. Our other services will request current tokens "on the fly" via API, which will minimize damage in case of compromise of any system component.Security Model and Encryption (Crypto Core) No secret should be stored in plaintext in the database. Upon application startup, a Master Key is passed to the environment variables. If the key is missing or has an invalid length, the service should fail at the initialization stage with a clear error in the logs. Each secret is encrypted before being written to the database using this Master Key. Upon request, it is decrypted in memory and returned in the response body.Audit Logging (Audit Trail) Any action with secrets (creation, reading by the service, successful or unsuccessful rotation) must be recorded in a separate log file audit.log (or a separate table in the database). Strict Taboo: It is strictly prohibited to record the actual values of secrets in the audit log (neither in plaintext nor in encrypted form).
We have a dedicated server on Hetzner with a website on Docker (+ Laravel framework) Contact with the developers has been lost Need to: - restore and change server access (probably SSH) - recommend a storage location and set up a full server backup with easy recovery, probably not on Hetzner for security - fix the logo that is not displaying for some reason (it's unclear why the file has become inaccessible) Important - there is no website backup, and there is no room for error. We will only consider experienced specialists.