Skip to content

Conversation

@AyushAmbastha
Copy link
Contributor

Before-

BeforePod

After-

AfterPod

Note: The description I've given for PVCs in the pods.tsx file is -
'A Persistent Volume Claim is a request for a resource i.e A Persistent Volume'

@openshift-ci-robot
Copy link
Contributor

Hi @AyushAmbastha. Thanks for your PR.

I'm waiting for a openshift member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@openshift-ci-robot openshift-ci-robot added needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. size/S Denotes a PR that changes 10-29 lines, ignoring generated files. labels Mar 27, 2019
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think we should use the PVC resource icon here since we don't use the S for secret volumes or the CM for config map volumns.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Typically we use it for a specific resource instance with a link as well, so we're breaking the pattern.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Which icon do you suggest we use then?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Honestly, I'm not sure having a different icon for every kind of volume (emptydir, hostPath, secret, config map, PVC, etc.) scales. It would be difficult to find meaningful icons for all of these. We might just leave it off.

If it links to a specific secret, config map, or PVC, it would be nice to have a link to that specific object with the resource icon badge.

@spadgett spadgett added this to the v4.2 milestone Apr 17, 2019
@spadgett
Copy link
Member

spadgett commented May 9, 2019

Hi, I wanted to check on the status of this PR. I think the simple thing to do is to add a ResourceLink for all types that support it (PVC, secret, config map), and use a plain text value for other types.

@AyushAmbastha
Copy link
Contributor Author

Hi, I wanted to check on the status of this PR. I think the simple thing to do is to add a ResourceLink for all types that support it (PVC, secret, config map), and use a plain text value for other types.

Hey @spadgett , Do you still feel that the Icon such as the 'PVC' one is not required and that Adding ResourceLink for all the ones that are supported, is enough?

@AyushAmbastha
Copy link
Contributor Author

Screenshot from 2019-05-27 15-25-44

@spadgett This is how it looks like after using ResourceLink.
Also, the 'Name' column deals with the group names for volume types such as PVCs etc , but not for Secrets. So the secret name will be displayed twice. Then again, the link cant be put on the 'Name' column as it wouldn't be correct in the case of Volumes and PVCs.
What do you think we should do in this case?

@spadgett
Copy link
Member

Volume name isn't always the same as the secret name, so we should display both.

The links should be like

(PVC) my-pvc
(S) my-secret

Make the actual name of the object the link text. This is consistent with other links throughout the console.

Thanks!

@openshift-ci-robot openshift-ci-robot added size/M Denotes a PR that changes 30-99 lines, ignoring generated files. and removed size/S Denotes a PR that changes 10-29 lines, ignoring generated files. labels May 28, 2019
@AyushAmbastha
Copy link
Contributor Author

Screenshot from 2019-05-28 14-01-09

Screenshot from 2019-05-28 14-01-51

@spadgett Made the changes as requested, Please review. For volume types in which neither the Resource link exists nor the className=fa-... is chosen, nothing is displayed and null is returned. Is that okay or - should be displayed?

Referring to line - https://github.com/openshift/console/pull/1344/files#diff-9f09cd1fb4d8499069d32d298cb76de7R21

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

s/link/kind

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This comment is outstanding.

@openshift-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: AyushAmbastha
To complete the pull request process, please assign rhamilto
You can assign the PR to them by writing /assign @rhamilto in a comment when ready.

The full list of commands accepted by this bot can be found here.

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@AyushAmbastha
Copy link
Contributor Author

/assign @rhamilto

@AyushAmbastha
Copy link
Contributor Author

/assign @rhamilto

@AyushAmbastha
Copy link
Contributor Author

@spadgett All changes requested have been taken care of. Please review.

Copy link
Member

@spadgett spadgett left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

FYI, it looks like this will conflict with #1891

const kind = _.get(getVolumeType(value.volume), 'id', '');
const loc = getVolumeLocation(value.volume);
const name = value.name;
const namespace = pod.metadata.namespace;
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You want to make sure you're getting the namespace from the original resource, not the pod template. I don't think it's always set here.

label: 'Projected',
description: 'A projected volume maps several existing volume sources into the same directory.',
},
persistentVolumeClaim: {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's unclear to me why this change is needed. I'm not sure it's right since there are other more specific values for different kinds of PVCs above.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This comment is outstanding.

@spadgett
Copy link
Member

spadgett commented Jul 9, 2019

/assign

@anmolsachan
Copy link
Contributor

anmolsachan commented Jul 15, 2019

@spadgett The contributor to this PR is no longer contributing to the project. Is this pr required or all the features are being handled in #1891 ?

@anmolsachan
Copy link
Contributor

@zherman0 The contributor to this PR is no longer contributing to the project. Is this pr required or all the features are being handled in #1891 ?

@zherman0
Copy link
Member

@anmolsachan - PR1891 adds a kebab menu to the volume table and allows for the Remove Options. In doing so, the volume tables were refactored to use the new PF style.
That said, no additional work was done on types in the table and no work was done with any volume icons.
I think this PR is still needed if this work is considered needed, but it will need to be reworked a little once 1891 merges.

@spadgett
Copy link
Member

Closing in favor of #2107

/close

@openshift-ci-robot
Copy link
Contributor

@spadgett: Closed this PR.

Details

In response to this:

Closing in favor of #2107

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants