📄️ How to create a Demo Cluster in GITA?
Creating a demo cluster in GITA allows users to explore and test the platform's features safely, without needing to connect a real cluster. It is ideal for learning, demonstrations, testing, and onboarding new users, providing a risk-free environment to get hands-on experience with GITA!
📄️ How to register on GITA?
1. Access the GITA registration page
📄️ How to Change the Password?
1. In the GITA panel, select the settings menu (shown in the figure below), in the top right corner and, then, the option "Edit profile"
📄️ How to Recover Access (Password)?
1. On the GITA login page, click on the "Forgot your password?/Forgot password?" link, as shown below:
📄️ How to Create a New Organization?
1. In the GITA main panel, click on the highlighted button below, "Create Organization":
📄️ How to Change an Organization's Name?
1. From the homepage, click on a cluster from the organization you want to change
📄️ Como incluir um usuário do GITA na sua organização
1. A partir da página inicial, clique em um cluster da organização que deseja alterar
📄️ How to Delete an Organization?
1. From the home page, click on a cluster from the organization you want to change
📄️ How to Create a New Cluster?
1. In the organization's main panel, the user should click on one of the highlighted buttons to add a new cluster to the organization:
📄️ How to Change a Cluster's Name?
1. Access the GITA interface and choose the cluster where you want to make the change.
📄️ How to Add a GITA User to Your Cluster?
1. From the homepage, click on a cluster from the organization you want to modify
📄️ How to Invite an External Person to Your Cluster?
1. From the home page (https://app.gita.cloud/home), click on a cluster from the organization you want to modify
📄️ How to Open a Cluster Console Session on Gita?
This Standard Operating Procedure (SOP) aims to guide users on how to access a cluster's console within the Gita platform, allowing direct manipulation of the environment via command line.
📄️ How to Have an Overview of Pod Status Across the Cluster?
1. In the cluster's main panel, the user should look for the "Details" button (highlighted in the image below), within the "Pods" box:
📄️ Client Proxy Configuration in a Cluster
This document describes the procedure for configuring a client proxy in a cluster, either during cluster addition or later, via settings.
📄️ How to Exit a Cluster?
1. Access the GITA interface and choose the cluster you want to leave.
📄️ How to Disable a Cluster?
1. Access the GITA interface and choose the cluster you want to disable.
📄️ How to Delete a Cluster?
1. Access the GITA interface and choose the cluster you want to delete.
📄️ How to Import a YAML?
This Procedure shows the import of a YAML (Yet Another Markup Language) which is a format used to define configurations and infrastructure as code, facilitating the standardization and automation of resources in a cluster. Importing a YAML allows applying configurations such as deploys, services, and permissions efficiently. During import, adjustments may be necessary, such as modifying names, updating container images, and defining environment variables. This ensures that the configuration is suitable for the environment before application.
📄️ Notification Settings
This document describes how to create a notification channel on Gita that allows the system to send automatic alerts according to the rules defined for the cluster. This ensures that critical events, warnings or important information are delivered to those responsible at the right time. Channel configuration involves selecting events, receiving intervals and the means by which the notification will be sent (e.g., Mattermost, Slack, Webhook, etc.).
📄️ How to Gain Insights From Events?
1. Through the sidebar, the user can access the events panel, as highlighted below:
📄️ How to View Financial Data? How does this Work on GITA?
Each user will have 15 free days to use GITA. After this period, financial data can be monitored directly through the platform interface. To view financial data:
📄️ Creating a Custom Rule
This Procedure describes how to create a custom rule.
📄️ How to Get Help?
1. On any platform screen, the user will find the help icon in the top right corner, as highlighted in the image below.
📄️ How to Open a Pod Console?
1. Access your Cluster Interface on Gita:
📄️ How to Compare Two Resources?
1. Access your Cluster Interface on Gita:
📄️ How to Edit a Resource?
1. Access your Cluster Interface on Gita:
📄️ How to View a Workload Graph?
1. Access your Cluster Interface on Gita:
📄️ How to View Pod Logs?
1. Access your Cluster Interface on Gita:
📄️ How to add CIDR-based access permission to a Cluster in GITA?
CIDR (Classless Inter-Domain Routing) permissioning is a form of access control based on a range of IP addresses belonging to a network. This functionality allows you to define CIDR blocks, making it possible to authorize access to a GITA Cluster only to desired IP addresses.
📄️ How to customize a cluster image in GITA?
Customizing a cluster image in GITA allows you to choose the version of the probes used, use images from your own registry (private, internal, or with specific cluster permissions), and have full control over the configurations and versions used in your containers, ensuring compatibility and security according to your needs.
📄️ How to get resource recommendations for workloads in GITA?
The Recommendation feature in GITA allows users to obtain CPU and memory requests and limits recommendations for Kubernetes workloads (such as Deployments), based on the actual consumption observed over a given period. This helps optimize resource allocation, avoiding both waste and resource shortages.
📄️ How to track resource usage of cluster pods?
1. Access your Cluster Interface in Gita:
📄️ How to set up two-factor authentication (2FA) for your organization?
What is 2FA?
📄️ How to inspect audit events in GITA?
The Audit tab in GITA allows you to view and track all relevant actions performed within the cluster, such as configuration changes, creation or removal of resources, and administrative events. It works as a historical record that facilitates audits, problem investigation, and compliance verification. With this data, it is possible to understand who did what, when, and what the impact was on the environment, ensuring greater transparency and operational security.