Skip to content
This repository has been archived by the owner on May 3, 2022. It is now read-only.

Can't deploy stateful sets with Shipper properly #131

Open
parhamdoustdar opened this issue Jul 25, 2019 · 3 comments
Open

Can't deploy stateful sets with Shipper properly #131

parhamdoustdar opened this issue Jul 25, 2019 · 3 comments
Labels
enhancement New feature or request

Comments

@parhamdoustdar
Copy link
Contributor

This came up when a user tried to create a stateful set as part of his chart. The problem is that we inject labels into the template within a deployment object, but we don't do the same for Stateful Sets.

As a result, pods created with a Stateful Set are never matched against the selectors inside a Service.

@parhamdoustdar parhamdoustdar added the bug Something isn't working label Jul 25, 2019
@isutton
Copy link
Contributor

isutton commented Jul 25, 2019

I would suggest changing this from "bug" to "feature" since management of Stateful Sets were never tested nor considered.

@parhamdoustdar
Copy link
Contributor Author

Good catch. I didn't realise "bug" was the default state.

@parhamdoustdar parhamdoustdar added enhancement New feature or request and removed bug Something isn't working labels Jul 26, 2019
@juliogreff juliogreff added this to the release-0.9 milestone Nov 28, 2019
@osdrv osdrv self-assigned this Jan 30, 2020
@osdrv
Copy link
Contributor

osdrv commented Feb 5, 2020

This task needs a generic example of a workload that could use stateful sets so Shipper can eventually advertise this model.

@juliogreff juliogreff removed this from the release-0.9 milestone Feb 21, 2020
@osdrv osdrv removed their assignment Feb 24, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

4 participants