Skip to content

Instantly share code, notes, and snippets.

View podnov's full-sized avatar

Evan podnov

  • USAA
  • San Antonio, TX
View GitHub Profile
@jbw976
jbw976 / OSD removal workaround
Last active August 22, 2021 22:34
OSD removal workaround
Remove k8s-nvme-01.acme.org node from Rook orchestration
delete OSD replica set, this will also stop/kill the OSD pod
kubectl -n rook delete replicaset rook-ceph-osd-k8s-nvme-01.acme.org
remove entry for k8s-nvme-01.acme.org node from the orchestration status map
kubectl -n rook edit cm rook-ceph-osd-orchestration-status
delete all node's OSD config maps: rook-ceph-osd-XX-fs-backup (93,94,95,96,97,98,99,100,101). example:
kubectl -n rook delete cm rook-ceph-osd-93-fs-backup
@odrotbohm
odrotbohm / gist:3141439
Created July 19, 2012 07:49
Proposal: Allow EntityManager(Factory) to be injected through a constructor.

When designing application components it's best practice to inject mandatory dependencies though the constructor and essentially make the application component immutable like this:

@Named
class MyComponent implements Component {

  private final Dependency dependency;

  @Inject
 public MyComponent(Dependency dependency) {