-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Redesign environment details page #142
Labels
enhancement
New feature or request
Comments
epmd-edp
pushed a commit
that referenced
this issue
Jan 26, 2024
Jira: EPMDEDP-13140 Related: #142 Change-Id: I37dcac6af4980d84aaf420dc2e595d537d6c413d
epmd-edp
pushed a commit
that referenced
this issue
Jan 30, 2024
* Previously, argo applications were handled manually * Now, when argo applications are setup after cdpipeline created, the previous logic is outdated * Since now, deploy pipeline run is created from TriggerTemplate which name is mentioned in stage.spec.triggerTemplate Jira: EPMDEDP-13140 Related: #142 Change-Id: Iae23f8549ac783ce52aa9366dbba52284796ccbb
epmd-edp
pushed a commit
that referenced
this issue
Feb 5, 2024
Jira: EPMDEDP-13218 Related: #142 Change-Id: I92a9a6ee33c17bca76af1edb774fa86b6217d0f7
epmd-edp
pushed a commit
that referenced
this issue
Feb 6, 2024
* Fix Edit feature doesn't work for a stage and pipeline * Fix Incorrect link to the Argo CD in stage * Fix After deleting the stage the user should return to the previous screen Jira: EPMDEDP-13240 Related: #149 Change-Id: I23954c94e2340fa022612a7156ee690944b40930
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Inspiration: https://codefresh.io/blog/introducing-the-worlds-first-dashboard-for-gitops-environments/
The environment page contains information:
General Overview. Get information from Argo Application(s) fields from labels:
labels:
app.edp.epam.com/app-name: demo
app.edp.epam.com/pipeline: demo <- Filter by this field to group all applications for CDPipeline
app.edp.epam.com/stage: dev <- Show applications for specific stage
use targetRevision (imageTag) to show versions
add argo application name.
Main Content Area:
Environment Overview:
Display a grid or card-based layout to represent each environment (e.g., development, staging, production).
Each card should show the environment name, a brief description, and the number of applications deployed.
Application Cards:
Within each environment card, display application cards.
Each application card should include the application name, version, health status, and synchronization status.
Use color-coded indicators (green for healthy, yellow for warnings, red for critical issues) for quick visual recognition.
Filter and Search:
Provide filters for namespaces, applications, and health status.
Include a search bar for users to quickly find specific applications or environments.
Detailed Application View:
Allow users to click on an application card to access a detailed view (right swap pannel)
(Under discussion)Show comprehensive information about the selected application, including labels, custom resources, and deployment details.
Environment Grid Cell:
Each environment grid cell represents a specific Kubernetes environment (e.g., Development, Staging, Production). The cell is designed to provide a quick overview of the environment's applications and their current status.
Environment Title:
At the top of the cell, prominently display the name of the environment (e.g., "Development," "Staging," "Production").
Environment Description (can be an icon):
Below the title, include a brief description or metadata about the environment. This could include details such as the cluster name, location, or any relevant information to help users identify the context of the environment.
Applications Overview:
Use a card-based layout to showcase the applications deployed in that environment.
For each application, display key information:
Application Name:
Clearly state the name of the application.
Version:
Display the current version of the application.
Health Status:
Use color-coded indicators from Argo CD (green for healthy, yellow for warnings, red for critical issues) to represent the health status of each application.
Sync Status:
Indicate whether the application is in sync with the desired state (e.g., using icons like a checkmark for in sync and an alert symbol for out of sync).
The text was updated successfully, but these errors were encountered: