Who thinks cutting a head off with an axe is humane? Right. Right now, I want a burger.  Are you vegan? Yeah, I'm a vegan. For one reason, I should not eat vegan. Are you against animal cruelty? I guess, yeah. Yeah, I'm a vegan myself, though. Are you fought? Do you support animal cruelty? I'm not really. Not really? That's... Okay, you're not really. You're unsure of you? I personally don't. I only eat free-range and organic meats. Oh, really? How do you manage that? Because I'm quite wealthy. You're quite wealthy, so you don't eat out? No, not really. Not really? So you're not really? So you're not really? No, I'm sure too. I normally eat vegan places. I do, eh? Yeah, I do.  Yeah, so I eat vegan. Does he really? What's the last vegan place you ate at? Well, yeah, I've been surprised. Yeah, I've had a vegan model. I also, for lunch, I can see as well that you like... You know, the vegan one... Oh, good work. You know the one? Good work, so you're working there? He's exceeded his cross-examination. What about you? This is quite cruelty-free. The farm is cruelty-free? Yeah, yeah, yeah. What about the slaughterhouse?  Yeah, I reckon. If you sedate him, I'll sedate him. So it's not cruel to kill now? So it's... You think it's okay to kill?  Is killing okay? It's all right. If it depends...  Why is that? They all have feelings. I think it's a bit different because... It might be different, but are they both wrong? Okay, so what's the difference between a lion eating its prey and a human eating like an animal? What's the difference between a lion shredding an antelope alive, you mean? Yeah, yeah, but that's just natural instinct. That's how it's supposed to be. That sounds quite cruelty-free. I think by being... I mean, do you care about what happens in nature in terms of morality? No, pretty honest. So why are you mentioning that? So are we not part of nature then? Are we not naturally like animals? Are you suggesting we should act how animals act in nature? Yeah, I think we should. So you don't look like a lion to me? Yeah, because I'm not.  Yeah, yeah. So when you see a pigeon, you pounce on them and eat them? Yeah, if I was... No, no, no, no, in civilisation, I'm saying. Yeah, due to societal programming, no, I wouldn't know. Okay. No, what was societal programming like? I just want to know if you act like lions act. Is that your metric for morality? No, because I'm not a lion. I'm a human. So wait a second. So wait a second. You used lion's behaviour to justify your own, didn't you? Yeah, because they're an animal. Is that logical to you? Yeah, because you see lions attack other lions. You can't attack other people. Lions do some horrible stuff. Why are you using them as the metric for your morality? That's what I want to know. Because they're the animals that are binding by their animalistic instincts. Is it only me eating that you want to copy from lions, or do you want to copy them, sniff each other's bum, say, attack other lionesses' cubs? Well, if you drink dairy, do you drink dairy? Yeah. Eat cheese? That's a product of bestiality. Is it? Yeah. How do they impregnate the cows? They don't impregnate the cows. They need semen to impregnate a cow. Why do you need to impregnate the cows to produce milk? Why does a human woman produce milk? Yeah, but you can use hormone to stimulate lactation. Well, they don't. They do. No, they don't. They get semen from a ball? Yeah. How do they get the semen from a ball? How do they extract it? I do. It's crude, isn't it? Yeah. There you go. You can say. Okay, is that not bestiality? No.  It doesn't matter. What do you don't think? That is... Look, it's a very... It's a very... It's a very... Look, all I'm saying is that you said bestiality. I said that dairy is a product of bestiality. It legit is. So, you don't think they use hormones to stimulate lactation? They don't use hormones in the UK? Why not? They don't need to.  Yeah, it's true. Estrogen... They impregnate the cow with semen from a ball? Yeah. She has a pregnancy, a nine-month pregnancy. Then she starts to produce milk for her calf. Yeah. Yeah. True. The calf is born. The calf can't drink the milk. The calf is taken, yeah? Yeah. So, how does that calf feed on milk, then, if it's... So, give them a formula. Give them... Doglet. Or not. That's all right. That's all right. You're asking questions. You're asking questions. You're curious. Why are you not vegan? Because I like meat. No, no, you can't hold him to a highest. You're not vegan either, but you do eat a lot of vegan food. I do, and I love organic meat as well. I don't care about organic meat. It's not. It's not. It's not. What slaughterhouse do the organic animals go to, even if you believe the farm is humane? So, what's it like in the slaughterhouse for the organic animals? Well, in my brand, that's what I'll say. They should cut it out of the axe or the cow. So, would you... That's not pretty humane compared to, like, the legs. Who thinks... Okay, don't wait a second. Wait a second, bro.  Yeah. Who thinks that?  You will, too. So, would you like it done to yourself? If that's how my death has to come upon me. Right. Right. Right now, I want a burger.  Let's just say I've got an option, right? I've got a vegan burger here, the one from Vegan Royale. I've got one that an animal has their head humanely axed off with. Yeah. What decisions should I make in terms of ethics? Well, whichever one tastes better. Because everyone tastes better for ethics. Look, when you're in Burger King, right, they've already killed the... It's too late. It's not like they've chopped it out. Enjoy the burger. Yeah, but you know what supply and demand is, yeah? Yeah. Yeah, but I think the supply will... You're paying someone to axe heads off so you can have a burger. But, I mean, if you eat the burger that's already been made... No, but you're paying them money to produce more axes to cut heads off. But, you know, they stun animals here first. They do cut... There's a lot more humane, like, let's say on a farm, if they're giving, like, space to roam. You only eat from the Bulgarian farm? No, no, no. Okay, then why are you telling me all this? To show that it's humane. Why does it matter? It doesn't matter. It doesn't sound like you're made to hear. You're choosing a situation that you don't even eat from? No, I do. I eat from it sometimes. When you're in Bulgaria? Yeah. So when you're out, what do you do? So that pepperoni pizza you just had answered? Yeah, I love it. Pepperoni from factory farm pigs and gas chambered pigs, yeah?  He's not a pig, is he?  Have you ever squashed an ant before? Yeah. What's the difference between an ant and a pig? What's the difference between you and an ant? Humans have idea of morality right and wrong. Humans have more emotional feelings. Exactly, okay. And a pig the same, right? The first one. Humans have the idea of morality right and wrong. Exactly, so shouldn't we... Shouldn't we... Exactly. Well, I don't deliberately squash ants. Yeah, but you can't avoid squashing ants.  You can avoid killing pigs. Have you ever squawed a fly? I try not to. Have you ever done it though? Yeah. I used to eat animals, bro. You used to eat me?  Six years, yeah. Do you think in an ideal world everyone's vegan? Would that be ideal for the animals? Would that be ideal for the animals? In your ideal world, do you think everyone would be vegan? All seven, eight billion people in this time would be vegan. That would be an ideal world. Virgin is possible. Is that real? Anything is possible. So is it probable? No. It's improbable. Because I'm having a hard time convincing you that cutting off animals' heads is wrong. You think I'm going to have a pretty hard time with eight billion people? Yeah.  I mean, it is. It's more humane than having them... I don't care if it's more humane. Just because something's more humane doesn't make it humane. Yeah, but it's still a better alternative than having them in fact. There's a way better alternative than axing heads off. Okay, so do you not eat free-range meat, then? Absolutely. No, because they haven't been killed in... I wouldn't eat free-range dog meat. Okay. I'm Chinese. I know, but would you eat dog? I would. I have a pet dog. You would eat dog?  If it was already dead, yeah. No, no, no. I asked if you would...  Yeah, if I was hungry, yeah. No, no, no. I'm not saying you're hungry. I'm talking about... I'm hungry, then no. Brett, okay, you're hungry, but you've got an option. No, he's meat. They eat their whole...  See how much it tastes nice. Exactly. So it tastes nice.  It would just be a substantial amount of protein, which helps a lot. You don't eat meat for protein? No, I do. No, you don't.  Aw. You don't care about protein. You don't eat meat for protein. You eat meat because it's everyone else's. But what if I did care? Well, sometimes I do weight training, and sometimes I calculate my protein. I get 140 grams a day. So how do you get your... Freddie, there is meat free with tiduses. There's artificial protein. What's it called? It's artificial. It's made of plants. You mean like lab-grown? I don't eat that. I really like the lab-grown meat. Have you had it? It's not accessible yet. But there's plant-based meat. That's cruel. And you eat that. I think there's a couple of ways to create lab-grown meat. One of them would be cruel, and there's a humane way of doing it, where you just take like a little scratch. So would you eat that? You can create an infinite amount of meat. People are farming the animal. It's just that way of doing it. No, but... Would you eat that? I wouldn't consider it. If you ended the chicken massacre by pulling out a feather from a chicken and getting a cell, I think it would be justified. I do that veganism. You vegan yourself. I'm not a vegan. Most people are not. What do you think about this conversation? Yeah. And you can say, well, these animals deserve protection. I'm against animal cruelty, but I pay for it and I eat it. Personally, I don't necessarily think that it's more of me wrong to kill an animal for them. I personally don't think so. Okay, and why? We are in a position of power. So what should we do with that power?


Hi all, now welcome to the Cloud Native Special Interest Group meeting. Today is May 90th and actually we reconvene after one year break in Special Interest Group meetings. So it's great to see so many people on the call and hopefully we will have even more participants in the next meetings. So the today's agenda is to actually discuss how we restart the Special Interest Group. How do we establish regular meetings and just have introductions. And another topic I put to the agenda is about Jenkins Kubernetes operator. So last week we had a great online meetup by Tomos and we could use this venue to discuss what could we do to help Jenkins Kubernetes operator project and how we could adopt more features there and how we could deliver changes in upstream. Okay, so regarding the Google Doc, how we usually handle that. Okay, so we have a Gitter Chat and in this Gitter Chat we basically post meeting link and meeting notes every meeting. So you can go here and find the Google Doc here and also just I'll post it in the Zoom chat. Thanks so much. Okay, but yeah, we have a chat where we can have all these discussions if needed. So how do we usually organize the meetings? We have a running Google Doc where we make meeting notes and everyone is welcome to participate. So this document should be open for comments if you want to add something just put it there and I think we could just begin. Since we have a lot of participants on the call, my suggestion would be to just have quick introductions and after that press it with the common agenda. Who would like to go first? I can go. Okay, so this is Marki, I'm not the ICDF Jenkins Zoom. Everybody for the CDF Zoom, that's actually me. My name is Marki. I am one of the Jenkins core maintainers as well as Summer of Code or Gatman and lead of the Pipeline Authoring SIG. I am also a member of the Kubernetes org as well as one of the release managers for all the versions that get released. I'm happy to be here. Thank you so much for bringing this back into the forefront Oleg and welcome everybody. Thank you. So I could also do a quick introduction then. So yeah, my name is Oleg Ninazhov. I'm one of Jenkins core maintainers. I'm also a Jenkins board member and the leader of a few special interest groups. One of them is platform special interest group and when cognitive SIG was running in the previous iteration, I was helping to organize the meetings, etc. and I'm really happy to see this special interest group back because for Jenkins being friendly to users running in the cloud is really important and this meeting, this meeting is a great opportunity to discuss challenges, coordinate projects and see how we could help each other and Jenkins users who run Kubernetes or in other cloud platforms. So nice to see you all here. Anyone else? Hi all, I'm Sumat. I'm actually working on one of the GSOC projects which is the external fingerprint storage and Oleg is my mentor along with Andrey and Mike. So that would be one of the founding projects I think for external for this SIG, the external fingerprint storage project. So happy to see you all and I'll keep you updated on my progress on that project. Thank you. Akram, sorry for the previous introduction. That's okay. So my name is Akram Binaisi. I'm working for Red Hat. I'm the maintainer with Shavad and Vihav of the Jenkins images for OpenShift and also the maintainer for three plugins that we offer OpenShift for Jenkins on OpenShift and a contributor on the Jenkins operator which is the topic for this call now. Thank you. So hi all, I'm Sladen. I've been an active Jenkins contributor. I've worked with Jenkins in the past with the Jenkins community bridge project and I'm also a student for the Google Summer of Code with the Jenkins customers should be in service. Yeah. So I'm really excited to be part of this special interest group and help in whatever way possible. So thanks everyone for coming here and we'd like to move this group forward. Thank you. So I can go next maybe. I'm Zered. I'm from Red Hat too. I think Akram said almost everything about what we are doing on Red Hat and related to Jenkins. So yeah, we are happy to see this community grow in a bit above. Around the operator, we started a bit working on it on our side. So we're happy to join. Okay, so I can go next. So this is Vihav. I work with Akram and Javi on the Jenkins OpenShift and the Plugins and I'm also a contributor with them. And on the side, I also contribute to Hellen and Akram from side to side. So yeah, that's it for me. Thank you. And hello. I'm Tamash from VirtusLab and I'm basically the guy behind the Jenkins Kubernetes operator. Okay, thank you. So yeah, we have a lot of people who work on Kubernetes operator. And yeah, this is great. So thanks a lot for joining the meeting. I know that Kubernetes operator has its own meeting, but right now we have a few conditions we need to resolve in our calendars. So it's great to have this additional call. I'll share my screen again so we can see the agenda. And you can see that there are some meeting notes and please feel free to add something if anything is missing because it's basically collaborative for a document. I'll quickly speak about Cognitive C2.0, especially for those who didn't participate in the first edition. There is a thread in the developer's mailing list about it. But yeah, we can summarize the status. The previous C when we started it was built around Jenkins architecture changes. So if you go here, you can see that there are projects like Plugable Storage, also Cloud Native Jenkins, which bolt down to stateless Jenkins, Jenkins file runner, and other such components. Then there is configuration as code and Jenkins Kubernetes operator, which was added there. But at that moment, the specialist group was not that active. So although it's formally listed here, I don't think that there were active discussions at the S6 venue at that point. So this is what we had in 2018-2019. Some projects got a good progress. For example, if you go to Plugable Storage, you can see that Storage 4.0 to some extent for logs was delivered. Also, we submitted some other projects and discussed changes in other areas. But yeah, at that point, we didn't go further. Same for Cloud Native Jenkins, we had Jenkins file runner and other components, but all is still under the development. Integration as code evolved pretty well, but I would say that at the moment, configuration as code rather has its own special interest group. It's registered as a subproject within Jenkins. And this approach basically has its own meetings every two weeks. The next meeting is tomorrow by the way. And it evolves pretty well. But again, this project was quite detached from the special interest group. And we even had a discussion about moving it to platform special interest group half a year ago. We didn't do the move. But yeah, I think that in the current state, it rather deserves to be a special secret. And Jenkins Kubernetes operator, yeah, people on the call know the current state address. We had a meetup last week with the summary. And thanks to Thomas and all other contributors, the project evolves actively. So it's great to see its evolution, a lot of changes are incoming. Hopefully, there will be the next release soon. But yeah, I tried this project last week and it works pretty well. So this is what was the scope of the previous SIG. And one of the problems why this SIG wasn't that active as we would like is, well, the first reason that it was hardly focused on the architecture changes. So pluggable storage, Jenkins, all of them presumed major changes within Jenkins. And it was quite difficult to find contributors who were interested in this area. So for new addition of the SIG, my proposal was to switch more on use cases for users and to not necessarily be cloud native. My proposal is to actually focus on making the SIG cloud friendly and making Jenkins cloud friendly. You don't have to have the Jenkins itself cloud native to get benefits from running in the cloud and to get benefits from the cloud native environments. At least that's my approach. And I would be happy to discuss that. So what do you think about that? What do you think about the scope for interest for this special interest group? I am a plus one. I'm sorry. I'm a plus one. It does make sense. But how will this, like you have mentioned integration with cloud native CICD engines like Acton, Jenkins. So how do you see this being implemented? Yeah. So it's a good question how it would be implemented. I can just describe my personal vision. So Jenkins pipeline is basically an engine within Jenkins. And even now we have multiple implementations of this engine. For example, when you run with sandbox or without sandbox, effectively you have different pipeline engines under the hood executing of your pipeline. And there is no blocker from making these engines extensible. And for example, making Tecton run a new engine. So for example, you would be able to run Tecton pipelines, but at the same time get all benefits from multi branch pipeline and all the harness around the core engine, which is available in Jenkins. At least in theory. So I think that's all the support that comes to the engine in the back of the Tecton base pipeline. Sorry. I might have missed the questions. Like my question was like does Jenkins X do that all the time? So the current state is that Jenkins X is a separate project. So Jenkins X is a project under the umbrella of continuous delivery foundation, actually same as Jenkins and Tecton. So if you go here, you can find that there are four integrated projects and one incubated. And all of them have basically they operate in the continuous integration and continuous delivery space. Moreover, there are some high level abstractions. For example, in CD foundation, there is interoperability special interest group, which specifically dedicated to ensure that the services can interact between each other. And for example, for this particular project, integrating with Tecton and Jenkins X could be a good subject for this SIP. Why I put it to the cloud native SIP scope is because Tecton and Jenkins X are cloud native CICD engines. So for me, it would be useful to have it in the scope. But yeah, full disclaimer that right now there is no real effort planned towards this direction. If you have contributors, we would be working on that. If not, then not. So yeah, this one, yeah, maybe it's an aspirational goal. But yeah, I think that in principle, it would be really beneficial to Jenkins users. And yeah, for example, if you go to the Jenkins roadmap, this is what we are currently building. So this roadmap is a draft. But the result of the section for Jenkins on cloud platforms. And here, for example, we have Tecton support as something in the future without no specific dates. Well, there is no dates there at all. But yeah, right now, it's a rather subject for the discussion. But if you're interested to contribute to this project, I think it's something we could discuss at the SIP meetings for sure. Any other comments? I can't mute that one. I'm not sure who is it. But everybody seems to be muted. Okay. Well, anyway, we cannot record and get muted. So yeah, this is the scope. And again, it's not something like we would be working on all these areas and discuss and call these areas at once. It's a scope of interest. So depending on the meetings on the schedule, we can set up topics. So for example, today, we discussed Jenkins Kubernetes operator, which is here. Next meeting, we can take a look at another topic. For example, Jenkins file runner of Kubernetes plugin and go in that way. But still, the SIP could be a good umbrella for all these projects. I think this is a great idea. I like this, adding this into the, to the scope. So yeah, if you're fine with that, I'll probably, after the meeting, maybe later this week submit a patch to this page just to adjust the areas for improvements, scope of interest, maybe tweak the projects a bit. But yeah, I think that it would be a good start to just start working this page. And the topic, which is quite close to areas of interest is about funding projects. Because as we already discussed, ticked on, it would be a great initiative in principle, but there is no ongoing work. But there is, there are some projects which are currently ongoing and the way we could do some collaboration even now. And we could use SIP in order to promote these projects to help finding contributors and the resolving obstacles in the Jenkins community. And I started from preparing a list of projects which are closely related and which are currently ongoing. So two topics, more or less no brainers for me because they come from the previous iteration of the SIP, those Jenkins operator for Kubernetes and Jenkins file runner. But yeah, there is a lot of other projects which we could discuss. And yeah, I suggest to quickly go through that if everyone is interested. Okay, so yeah, the first project in the list I have is a project by Sumit about external fingerprint storage. So we started it as a part of our JSOC effort. And if you go to the cloud native 6.0, there is a plug the storage page. So yeah, there is a lot of storage types and fingerprints is here. Why it's important because if you want to do CI CD, you likely want to have a kind of traceability and observability of your artifacts inside Jenkins or outside Jenkins. And if you move outside, especially if you want to build a system on the top of Jenkins, having an external storage would be great. And right now we have ongoing discussion how it would be implemented. And maybe Sumit, you would like to summarize what would be the current plan. Hi, so basically under this project, what we are targeting for is first that we're trying to move, we're trying to add an extension point which can allow, which can allow code to support external storages. Second, that we are trying to build a reference implementation for Redis at the moment. And third is that once we can do both these things is that we can actually trace these fingerprints across different Jenkins instances. So that is the core idea for our project. And right now we are like in the first week of it. So as we go on and develop it, we'll post more updates on this. So Oleg, do you have anything else in mind that I should be talking about? Is that good? I think it's a good summary. Thank you. So what's the opinion of other participants doing it to a pluggable storage? And if so, what's your opinion about this particular topic? Can I ask you to develop just what is it supposed to be in terms of usage? Just I'm reading right now the page about it. It's about tracking usage of artifacts, credentials, files and so on. What do we mean by tracking? So basically in Jenkins there is a database called fingerprint storage. Well, this is basically a bunch of files on the file system right now. It's not a real database. And it posts different metadata about artifacts. And this metadata is extensible. So for example, you can trace Docker images, you can trace artifacts. And finally, just ends up accessible to Jenkins users to Jenkins jobs so that they can do something with this data. For example, you can trace usage of your artifact or of your image container across multiple jobs, if needed, or within your delivery pipeline if you use it across multiple jobs. Okay, so let's try to give a simple example. Imagine that I built like a simple Java web application and I referenced some Maven artifacts in my Pomex MN or something like that. The Jenkins pipeline will trigger at some point the build of my Java application. Will any of my Maven artifacts, for example, will be referenced in this database? And would it be the same for any thing that I build every class, for example, that I build or compile? It really depends on the implementation. For artifacts, when you publish an artifact, it can be automatically added to the fingerprint database. And what it means, you have one job which builds your artifact and another one which deploys it to a server, for example, new release of your library of your service, and then you can trace this dependency. Or another use case, let's say just staging so you can pass your artifacts through environments and again trace usage, trace build results and test results within these environments, and query this data within Jenkins so you can quickly access what happened with this artifact. Okay, what is the fingerprint that is taken? Is it like an MD5 or SHA-256, something like that, or every file? Yeah, so yeah, I'll probably dive to the code a bit. So in Jenkins, there is a fingerprint class written inside Jenkins code. And this fingerprint class is basically an item which has ID, basically MD5 at the moment. And it also has an extensible set of fingerprints. Yeah, sorry, facets. So a facet is basically an extensible object in Jenkins, and any plugin, any step can put additional information in the fingerprint. So you create an artifact, you have a unique ID, and then any instance within Jenkins can put additional details there, which can contribute to user interface, which can be either the query in the future. And yeah, this is basically the instruction. So it really allows to do everything as long as you have for a unique ID. Okay, do you have already an idea of what would be like the default implementation? I mean, which kind of file will be tracking? Just asking because of performance, for example, let's say you have a very naive approach, like I would track all the classes or all these things that I built during my pipeline. So it would be a huge amount of CPU to just compute this all the time. So I do have an answer about this right now. Sumit, what do you think? Yeah, just for example, for a simple web application, let's assume, for example, that I want to know that which any class of all my dependent maven jars, I want to know which one I used. So I will get every jar extracted, get the MD5 for every class inside, and I will store it in ready sorry, in the file system or whatever. So this could be very CPU consuming and probably even for bigger application, it will be storage consuming. So what will be the implementation for this? Will it be distributed? Will it be like running inside of the pipeline? Will it be a synchronous or synchronous? Would it add yeah, this kind of questions asking right now. So I'm just trying to understand maybe what kind of usage we have for this. I see a lot of data and CPU cycles. But yeah, right now I don't know what kind of usage we can have. So basically, like from what I understand is that so basically, whenever we want to fingerprint a particular file, that is an extra build step that we do add on our own. And fingerprints by default, like they are very small in size. So they don't take a lot of space. I think Jesse ran some tests for those. And so I think, in fact, from the current implementation, all these fingerprints are as it is in Jenkins home, right? So they're already, it's not a good way to be storing Jenkins because so fingerprints because so we are dependent on the storage disk of Jenkins home. So by taking it out of there into an external storage, like, I think that is an extra step that is much better. That is actually solving a problem. And as far as I think the database was like, we can configure it's more easy to configure the database to, you know, have maybe replica sets or any other such things that we would want. So like, maybe, maybe I think I don't know if I answered your question or not, but that would be my take on that. Yep. I would all say that the implementation is yet to be seen. What we mostly target in the pluggable storage stories is offering extensibility APIs. So for example, what we did for artifact manager two years ago, we created extensibility API. And then, for example, Microsoft Azure team, they have experience with working with Azure storages. And they created a reference implementation, well, the implementation of the APIs for Azure, same for AWS, etc. But our main problem was to first provide architectural capabilities so that the users could do so. And to answer your specific use case, it really depends on what you run and how you index fingerprints. If you want to index every class in your file, you totally can do it in Jenkins. But yeah, it comes at cost. But the Jenkins want to index it like that by default. So it's your educated choice as a user, if you want to do that. You have Jason on the call. Yep. Hi. Just here to see if there's anything I should add to, but probably not. Okay. So, yeah, we spent some time on this project. I suggest that we slowly move on. And we could have a special session at the next meeting about the storage because it's an interesting topic and we could deep dive. And I guess it would be really interesting for us to meet other participants in this project because we really seek for the feedback from users so that we can plan our work. So other projects which we have on the list, one is Jenkins on Kubernetes. So just to explain the history, right now we have a lot of stories about running Jenkins on Kubernetes, but basically no documentation on Jenkins at all. No solution pages, no guidelines, nothing. And in the documentation seek, we identified it as a priority project. And we started from doing online meetups about Jenkins on Kubernetes, but we also want to have some documentation, to have some solution pages so that we can share this experience. And we want to integrate this knowledge and make it accessible to Jenkins. Obviously expertise of cloud native seek members would be essential if you want to deliver on that. So it's a kind of joint project between two seeks. And yeah, hopefully we will have contributors for that even during the next week. We have UI UX hackathon and this project is proposed there. And what else? And yeah, we also have plugin projects. So for example, Marky who's in the call he's a maintainer of Kubernetes plugin or Prometheus plugin. And this plugin is actually measure the seeks scope. And yeah, Marky, what do you think about covering these topics, topic periodic, the seek meetings? Yeah, I would love to do that. Yeah. So yeah, exact list of plugins is yet to be seen. But I think that this area would be really interesting for potential Jenkins users. And we can also see how we could collaborate, because for example, yeah, there is Jenkins Kubernetes operator, it uses Kubernetes plugin. So probably we could find a lot of collaboration opportunities there. I'll skip JCask for now, because it's a subject for longer discussions. And yeah, so we have 20 minutes left. Should we just switch to the Jenkins Kubernetes operator? Or would you like to discuss the logo? Because we don't have one. Yeah, so, yeah, right now what you have for this fancy icon, it's looks especially fancy when you zoom in or when you post it in Twitter, because it's something like 128 pixels. So my proposal was to actually reuse existing artwork. And the best matching thing is this logo. So I would suggest something like that. But if you have ideas, what it could be, I'm happy to discuss them and probably to put something else. So just think about that. My plan is to actually start mailing list thread about updating it. So if you have any ideas, please share them in this thread. And then, yeah, sorry for all these editors. And I think now we can actually switch to the Jenkins Kubernetes operator. So last week, we had a presentation by Tomas. All materials are already published. So you can find it, for example, if the comments ever load. So here you can find a video recording is this presentation and demo by Tomas. And let's just second, I started getting an audio also you can find slides, et cetera. And one of the topics we discussed with Tomas is what would be the opportunities for the seek to help and how we can generally help the project to move forward. Because right now it's a part of their roadmap. There is an old Jenkins enhancement proposal, which documents what would be implemented and what needs to be implemented. And I think it's a good opportunity to discuss a way we could help in order to move this proposal forward and to find a good finish and maybe switch to next iterations and help in other projects. So Tomas, would you like to quickly talk about the current status and what changes you hear? Yes. Okay. So the current status for the Jenkins Kubernetes operator that we managed to run the Jenkins on top of Kubernetes with a bunch of Jenkins plugins, for example, Kubernetes plugin or Kubernetes secrets plugins, which nicely integrate the Kubernetes itself. So we use the operator pattern for that. We have some issues with the Jenkins itself. So in my opinion, the most important thing that the Jenkins is application, I would say stateful. So we have to care about the state. So with the current Jenkins architecture, we have to make a backup of some files from the Jenkins home directory. And we have to know about the really deep internals, what, for example, that file do, or we have to keep that, or just we can skip, we don't know. So this proposal for the Plug-Able storage is very interesting for us because we can move storage or state to another place and make the Jenkins provision by the operator be stateless. And we can run multiple instances of it and also make the high available because with current architecture, there is can be one Jenkins master and we can spin another Jenkins master without tearing down the previous one. So this is the most important, I would think. Another issue is that the installing plugins can be improved. So there is a download center, which only have information that, okay, you have Jenkins with version X and you can install those plugins. But there is no such thing like dependency tree, or in my opinion, we need some another API for the plugins to give you some use case. So from the operator perspective, I want to know if the user want this plugin in this Jenkins, and after making some API calls, I can verify that this plugin won't be installed for the Jenkins. And I want to inform user that, sorry, it's not possible because something like there is no dependency or it's not supported in your version. And we face a lot of issues related to that. For example, user put the plugin list that want to install on the Jenkins, the operator tried to download all these plugins. So it's on the directory. But after running the Jenkins, the Jenkins would say, I can run these plugins because I have some kind of dependency. So when I have this some kind of API, I think it should be something totally different. It will be very user friendly because we have information that user, this plugin won't be installed in this Jenkins. So the state, the plugins, we, I would say very heavy user of the Kubernetes plugin. So I can speak that this plugin involves very well. So yeah, there is a lot of diagnostic logs there. So the user have more information what's going on because in Kubernetes, there can be a lot of issues related to some volumes can be mount or basically it doesn't exist. So this information is now available on the log. So that's fine. So it's, you don't have another person expertise. So you have on the log. So you will be free. I have more free from supporting running Jenkins on top of Kubernetes. Yeah. And I think that those two things is most important for me. Yeah. So if you don't mind, I'll start from installing plugins because yeah, you're totally right. There is no API right now for dependencies. And my question to you was whether you need the API or whether you need the tools like for example, CLI tool does make a difference for you because for example, we have a project called plugin installation manager tool. And basically, this is a new advanced tool which supports basically manager plugins and it already includes some features which are not available. For example, in plugin management scripts within Docker, like your updates, your security updates and technically we could integrate dependency tracing here as well. Yes. I saw this project. So it's for sure better that using the install hyphen plugins.sh from the Jenkins Docker image. But still, for example, in some new cases, this tool have to download the plugin first, unpack this and read the dependencies from there. If we have API for that, we'll be very, the servers which hold the plugins will be more relaxed. So yeah, even Jenkins self will benefit from this kind of new API. Yeah. So right now we have a special plugin site, plugins Jenkins.io. And actually, this site has two parts back end and front end. And back end part already can supply the CPIs, the problem that the CPIs are not really documented. So for example, what you see here, these dependencies used to come from the back end site. Right now we have static sites. So it's just generated on the run. But still, we could expose these APIs if needed. So there is a project, just second, this project called plugin site API address. So again, it's totally not documented. But in principle, it has APIs which might be needed for your use cases. And you can deploy it locally, it can cache, it can cache the update center file and provide additional search queries if needed in the future. So for example, plugins and plugin end point. And this end point, it returns a lot of information, but this information includes dependencies. The question is, this API runs somewhere over the internet, exposed so I can just use it or I have to run this in Docker or something like that. Yes, right now you would have to run it. If needed, we could discuss creating a service for that. But there is one downside of running it as a service, because this plugin site API gets information from Jenkins Update Center. And let's assume you have a custom update center in your company, then you won't be able to use the same plugin site API, instead of that you would have to run your instance and connect to that. So in principle, having a public instance with this API would be doable, but in practice for some cases you would need to have a, you would have to run an instance anyway. I see. So yeah, that's interesting. So for me, I would try to use that and see what API I can get, what information and test if that will be enough for the operator basically. Before that, we had some discussions, for example, about having GraphQL engine for this component, etc. Later, we actually moved on because we just decided that we would rather generate a static plugin site. And if you go to this service, it's fully static now, it runs behind CDN. So it's also extremely fast. And well, we don't regret this decision, but still the API services obey if needed. So technically, we could add additional functionality there. Sorry. I have a question regarding the plugins installation. So right now with the operator, there is an issue about some user complaining about every time we will have to start Jenkins using the operator. Right now, we will download the plugins that the user would like. So in OpenShift, for example, with the OpenShift image, we got a different approach, which I think probably more fits more with the Kubernetes approach and the container image immutability principle is like we build the image with the set of plugins that the user wants. And then this image is stored in the container registry, the Docker registry. So every time that we want to redeploy the exact same image, we just deploy this image, and we don't have to care at every deployment or every startup to re-downloading the plugin, checking the dependencies and so on. So this one is done once. I wanted you to share this view and have some feedback from the group here to see if this approach for downloading the plugins on every startup, what is the use case behind this? Is it something that we would like to continue on on Kubernetes? It's a subject for continuous holiwar. So for example, personally, I'm also a big fan of immutable images, and I'm submitting control to DevOps world describing how to do it with Jenkins and Jenkins tools. But there is still some use cases where you might want to install plugins on demand. So the first use case when you have users, and like for example, Kubernetes operator, users define pipeline and define which plugins they need. So basically, you will apply the SCRDE and then whatever magically plus Jenkins instance, we set a required set of plugins and execute that. So you will have to install the plugins, but assuming that you have a local update center, it can be done quicker. Another use case is to just rebuilding and provisioning multiple images. It might have a value, but it really depends on what you want to build. Okay. Regarding the first scenario, I'm not sure to get it properly. So are you talking about the pipeline where we decide to install a specific plugin while we are running the pipeline or before starting the pipeline, something like that? Yeah. So imagine you as a user, if you're able to define not only a pipeline, but also to say that I need these plugins for my pipeline. And you wouldn't have to go to your Jenkins admins and to ask to install, for example, HTML publisher plugin or un-plugin for what it works. Technically, this use case would make sense. So dynamic installation of plugins, which you need. For example, we support this use case in Jenkins file runner, where a user can define a list of plugins and they get installed automatically. I don't use this mode, but it's possible. So probably my knowledge about Jenkins here is limited. But let's try to follow the HTML publisher example. Just imagine that the user, his pipeline or his configuration, he says, I want HTML publisher version 1.x. And the Jenkins version is running already 1.8. Okay. So it will want to kind of upgrade the HTML publisher plugin of the running Jenkins instance. And in most of the cases, that would require a Jenkins restart, right? Am I correct? Yes, if you run on the same instance. But for example, if you use Kubernetes operator, if you follow Thomas's example about availability and provisioning instances on demand, again, you can provision your Jenkins instance with a required set of plugins so that you can execute this payload. Yeah. But in this case, we just return to the same original problem. If it's just about instantiating another Jenkins instance from an existing pipeline, we'll be starting a new image. And so we can just consider that this image should have been existing before, or we can decide to create this image for subsequent restarts. I mean, if we're just in the plugin, we have multiple runs of the plugin, we will not build again and over again the same image, knowing that we'll be using the same version of the plugin set inside. So yeah, this is kind of the inception. But yeah, probably, as you said, it's like a long debate. Yeah, probably it will come back often because we had this discussion probably in the past and some users are coming with it again. Okay, let's put it for further discussion also because we are probably running out of time and there is other topics also. Yes. I have a few more questions regarding plugins. So from the operator perspective, the user defined the list of plugins they want to install and operator tried to install that. But the user want the exactly versions of those plugins and I find the only way to achieve that is to install plugins before starting the Jenkins with this CR tool or install hyphen plugins.js file and then Jenkins. When I try to install plugins directly from the Jenkins itself, it always install plugins with the latest version. And the question is why I can't specify the previous version of the plugin when installing from the Jenkins itself? I guess it's a user experience aspect which could be addressed because that's how current Jenkins plugin manager works. Speaking of that. Yeah, this is very problem for us because we have to restart all the Jenkins to install plugins. But when we have opportunity to install specific version from the Jenkins API through the Jenkins API, so operator can use that, it will be super easy for us. So with some kind of scenario, we don't need to restart all Jenkins master and just install plugins on the fly. Yeah, in some cases it will work. Well, you can install a new plugin dynamically. You cannot update a plugin in Jenkins. So in order to support that, you just need a proper REST API or CLIs and they could be definitely added. I'm not sure whether we have support for that in the default update center, but yeah, basically it's a small matter of programming. If you want to add this API, I think it would be totally doable. And I think this behavior comes from what we got from the download center. I think there is only latest plugin versions. I debugged this one year ago, maybe has changed. But yeah, I see that the root cause of that is the latest versions in the download center. It depends on the update center because even in Jenkins, we actually have multiple update centers. So for example, if you go here, here you have experimental update centers, current update centers, LCS update centers, which provide different sets of plugins. And it would be totally doable to have version update centers and support versions right inside these files. So yeah, you have to do the right. If you go here, you can see that there is just a link to whatever version, which is latest version supported by this LCS baseline. But if needed, Jenkins could download another version because all versions are still available in archives. So it just needs logic to retrieve that. It's not a problem with this particular version, it's not a problem with dependencies because you would also need to resolve dependencies. Most likely you would get into conflicts there. So it's doable, but it requires some design. Yes, I see. And we've got this new API. We even can check if it can be installed on your Jenkins or not. So yeah, this will be very much more user friendly for Kubernetes operator users. Yeah, we could add these APIs. And if anyone wants to contribute, it's something quite rocket science. So in Jenkins, we basically have two classes update site and plugin manager. And both these classes already have the APIs for different use cases. So we could just add the rest API there. And also include all dry run logic, et cetera. So for example, do it's definitely not a good example. But yeah, all API is already there. And we can add more APIs if needed for use cases. And I believe that if added this feature, for example, yeah, pre-validated configuration, it's already existing API, which, well, it's not API, it's not client friendly API, because it's designed on the four Jenkins tunnels. But we can expose API, which would be consumed by C-like clients if needed. And yeah, we can add features that you can prioritize these APIs. So we could implement what we need. Or somebody could implement, we just need to report these issues and to see whether anybody would be willing to contribute to this area. Tomos, if you would be willing to report the issues for that, it would be nice so that we can process them and maybe facilitate contributions around that. Yeah, sure. How is the process for creating the issues? Is the Gira ticket or GitHub issue? Gira ticket. So Jenkins Core lives in Jenkins Gira. And we don't have a plan to move to GitHub issues at least in if I see it in the future. Okay. Thank you. Okay. So, yeah, we're already running covered time. Sorry for that. So my proposal for the next meeting, I plan to start another doodle so that we vote for regular meeting time. I wanted to start from something like meeting every two weeks. Again, we will set up topics for particular meetings. So there is no need to participate if you're not interested in topic. Let's say next time we do external fingerprint storage. So everybody is welcome to participate. And then in two weeks we will do Jenkins father-runner or Jenkins Kubernetes creator again so that we will keep running these meetings and inviting contributors who are interested in particular agenda. Does it sound good to you? Okay. Then I will just get it implemented. So, yeah, thanks to everybody for your time. And I will publish the recording of this meeting. And if you have any feedback about what topics you would like to consider, just put them in the agenda document. So there are what they will do. So I will just put a section for next meeting. So if you want to discuss something, we just, you can just propose a change there and we will coordinate what we discussed there. For example, external fingerprint storage. So, yeah, that's it for today. And thanks a lot too much for sharing the feedback because, yeah, I knew about the plugable storage story. I didn't know about plugin manager aspects, but it's great to have such insights. Yeah. Thanks all. Thank you guys. See you. Bye. See you next time.


Hey Psych2Goers, and welcome back to another video. Thank you all so much for the love and support that you've given us. It's enabled us to make yet another exploration into everyday psychology. So let's begin. What do you do when you know that you've upset someone? Or what do you expect others to say when they cause you hurt? I am sorry. These three words wield the power of a magic wand. Apologies help renew trust, soothe emotional wounds, and repair damaged relationships. Sincere apologies are key to maintaining a strong, healthy, and meaningful relationship. So why is it so hard for some people to say they're sorry? Fake apologies can feel just as bad as never resuding an apology at all. Fake apologies are manipulative and oftentimes very confrontative. Some people get defensive when you tell them that they've done something wrong and they may react by denying it, playing the victim, making excuses, or shifting the blame onto someone else. With that said, here are seven tell-tale signs that can help you spot an insincere apology. Number one, I'm sorry, but I'm sorry, but I never wanted to do this. I'm sorry, but there was no other way. I'm sorry, but this hurts me as much as it hurts you. Any of these sound familiar to you? An apology followed by a but is a definite red flag. Though the other person is saying they're sorry, they're not really apologizing as they should. Instead, what they're really saying is, I'm the real victim here, not you. I'm hurting too, and my feelings matter more than yours, making you feel like you have no right to expect an apology from them. Two, no, you're taking it all wrong. Have you ever been told you completely missed the point or they're sorry you took something the wrong way? It may sound like a genuine apology at first, but don't be fooled. All they're really doing is acknowledging there's been some sort of miscommunication, but they're not sorry at all about what they said or did to you. They think that just because it wasn't their intention to hurt you, there's no need to feel bad or offended. Three, I'm sorry that you're so sensitive. Do they accuse you of overreacting or say it's not that big of a deal? Do they make it your fault, saying you're being too sensitive when they hurt you? What they're actually doing is trying to shift the blame from them to you by saying that you don't know how to take a joke or you get hurt too easily. They're showing that they lack the empathy to see what they did wrong. What's worse is that they somehow think it's your fault for feeling hurt. Number four, I'm sorry you feel that way. Look, I'm sorry you're hurt, but it's not my fault you feel that way. Wait, what? Anyone who says they're sorry about the way you feel instead of saying sorry about what they did is just trying to defend themselves, not atone for their bad behavior and because they don't want to own up to what they've done, they will try to invalidate your feelings and make you believe you have no one to blame but yourself. Five, I'm sorry you think that. Next is the I'm sorry you think that kind of fake apology. Though it may seem genuine to some, it's nothing but outright manipulation. What they really mean is that you're wrong in your thinking and they're right. They're asserting that they are not at all to blame for the way you have misinterpreted them or misunderstood their actions. They're not taking responsibility for their mistakes but rather forcing you to take responsibility for your perfectly valid feelings. Number six, okay, I'll apologize if. If you've ever fought with a sibling or a classmate when you were younger, you might remember saying these exact words, especially if your parents or your teacher forced you to say sorry and make up. And though the words I'm sorry have to come out of your mouth, you didn't mean it in the slightest bit back then. So why believe someone trying to do the exact same thing to you now? When an apology comes with conditions, the other person is most likely just telling you what you wanna hear. So you'll get off their case or try to get you to apologize first and take all the blame. Definitely sounds like a deal more than an apology. And number seven, I'm sorry, but I only did it because of you. I only said that because you started it or I only did it because you made me. Now, does that sound like someone apologizing? It sounds more like accusing, right? Instead of saying sorry like they should, they're trying to put the blame on you and make you out to be the bad guy. What this fake apology means is, look what you made me do. This is not the person that I am or the way that I usually behave, but you made me like this. You forced me to act this way. They are in denial of what they did and lack the self-awareness to understand that.  Suffice it to say, this is as fake an apology as they come. In the end, while it certainly means a lot that the other person would say they're sorry, there's definitely a right and wrong way to go about it. An authentic and heartfelt apology isn't about finding someone to blame or justifying your wrongdoing, but rather showing genuine remorse and owning up to it. When the other person sees how much you mean it and they feel like they can trust you again and move past what happened, then they'll come around. All you need to do is say you're sincerely sorry. Can you tell the signs of a fake apology? Which fake apologies mentioned in this video have you received? What do you suggest for making apologies sincere? You tell us in the comments below. If you found this video helpful, remember to like and share it with others. And don't forget to subscribe to Psych2Go for more psychology content. As always, thanks for watching.


Hi Gallia. It's really a pleasure to be speaking with you today. I always think about your practice and your teaching as bringing things together whether you know bringing the social and the artistic or the high and the low or the north and the south and I'm very kind of curious or wanting to ask you more about how this this impacts how you think about practice and you've constructed your own approach to both architecture and teaching. Things that we think as opposites, you know, art and social elite and expression are popular and elite and also virtual and physical. Right now. So the idea is always like if a new medium comes into play, let's say photography, then painting may die. And so in the 1900s, people would make the case that photography would displace art and painting. What happened is actually the contrary with the advent of photography art and painting in particular exploded. We did not have a it flourished and we have not had a moment more prolific in the art world as after 1920. And so what I would say is that this moment and as I prepare the class for I prepare the seminar for art and social infrastructure, the virtual actually will make the physical more relevant. We will have much more offers that are virtual but the moments in which we meet in a seminar will be even more precious than they are. People will have will make an effort to go to a seminar and meet in a group where you have 12 people or 20. And so what I predict is never a good word, but what I see is reevaluating of those interests and the word reevaluating it's very important to me because I'm teaching about values and I think that one of the things that we architects do is materialize the values of the time. And so I think that my relationship with the art world it's not from the point of view of art as an elite thing, but art as a value for all of us. And the reason why the art world has exploded in the last 20, 30 years it's because it's one of the mediums where more people communicate in and so it's in a in a network society where people come to it from different backgrounds, from different languages, from different ideologies art, it's still something that builds up consensus. And so it's really teaching it's really about updating myself in the consensus of the moment. And what's great about Gallia, your sort of contribution, analyst contribution to G-SAP and the school is this kind of dialogue that you've created between your practice and your teaching and this feedback group, which has been incredibly enriching to see grow and expand and as you've built more and more and design more and more for the art world or art collectors, etc moving increasingly in the public realm with your own practice and how you've brought these questions to bear upon your studios and your seminars.  I think of you as someone who has constantly made choices in terms of the kinds of practice that you want to have and you bring those questions to the students. And so two questions, one is where are you taking your own practice and what are you excited about? And then in relation to that where do you think practice might be going for the next generation of students and you know, what is exciting for you to imagine in light also what you just said, the physical is more is craved more than ever right now. Exactly. So I think of practice as opposite to size. It's not about how big anything is, it's how intricate it is, how you are connected to it. And so I could not imagine teaching if I was not a practicing architect because that's the medium in which I express the bulk of my interests and so you're right, I design the office to feed a way of being and a set of values that are with me and it has shifted over the years from working with artists to working with collectors to working with institutions to designing exhibitions to decide now museums and things like that. But it's not about whether let's say a children's museum for that it's for thousands of people today in the middle of Manhattan 80,000 square feet. It's not about the size of that versus an exhibition of the marginal artists from Paraguay in a museum of American society, for example. It's not about size. It's about the connection and the intricacy of the relationship of that particular thing and the values of that particular thing and the way you communicate to other people. And so for me there's no distinction between urban architectural or ergonomics or design. It's all within the spectrum. And so it could be a chair a bench in a public plaza or it could be a reconsideration of a downtown of a city passing through the scale of residential architecture passing through the scale of institutional architecture. All of those things landscape environment they all connect. They are all part of thinking and I feel like we have a repertoire of ideas all anew. And it's also not about the latest idea. Some of the considerations that I'm putting forward now with my students and my work are 1,000-year-old ideas. My interest of working with Bricks and Mesa reconstruction, you can trace that back to city and architecture thousands of years ago or Mayan architecture thousands of years ago. And it connects to El Adiodieste in Uruguay 40 years ago. And so I think the idea of pass and present, big and small, intricate or large. It's not we are too used of thinking about dualities and at this moment it's about increasing the repertoire of ideas and increasing the spectrum of people working together. So I think another thing that we are very strong at Columbia is at the sense of working as a team and not as a kind of you know divisionary architect. We are we are like a team school and we have been a team school for a while. And the last thing that I want to ask is so you you went to Columbia. Actually, I remember you talking about your Brick project you know very early on I think what you you had just graduated. So I love that you're coming back to that and and that the life of an architect as a practice is a kind of sort of spiral. What about New York?  Do you think learning coming to New York to be in an architecture school is important? How do you think the the the city figures at GESAP and in the way that you teach for example? Absolutely. I think that the intricacy of connections in New York cannot be replicated someplace else. I with the with the spread of the virus I have been receiving emails from people that live in rural Argentina three hours away from the closest airport like I have castings that are doctors and and pharmacists and teachers in uh Hernandez or Rodin three hours from an airport five hours from an airport and they have two cases of coronavirus in a town of you know Very far away and so I think even though the network is super extensive and super connected and intricate the node of connections that happen here in New York and the intensity of discussions and the ability of uh, you know Gathering that data that happens somewhere else and then immediately putting it in context with ELAS for example the Institute of Latin American Studies Sending that to them connecting to people uh, and so I think whether it's in architecture or whether it's in um international affairs or whether it's in law uh being in New York We can talk together online here and it feels like you would have to screen uh, you know for days In uh far away places to be heard. So I think here it just takes Like that and and things get connected immediately. And so I think the it will be New York will have it come back. It will definitely go a couple of states back and then forward But I don't um I've been here. I've been here through the 1988 crisis um 9 11 Superstorm sunday the 2008 crisis and uh, and every time Um, I have been in New York again and it has come back um Stronger and so I I I think that um, we are going to be hit very strong right now, but it will we will come back Um, and we will be relevant again Gallia, thanks so much for you know your optimism and But also your perspective. I really feel like you bring an amazing perspective to the school and to the students and I'm very excited to be together again in the fall and to Imagine come back over and over again as stronger As we think about how we're going to live in the future. Thank you so much Gallia. Thank you Amal. Have a good time. Yes. Bye. Bye


What is going on guys welcome back to the channel and I appreciate you being here today I bring you another destiny to video and today I bring you new last word gameplay via a new trailer That's just being dropped and also news and slight footage of a new hand cannon coming with season of the drifter an old school fan favorite the phone People but before we go any further guys if you enjoyed the video Show support you can by hitting that like button if you are new around here and enjoy daily destiny to videos be sure to subscribe Okay, so bungee just dropped a trailer for the draw quest which comes tomorrow the 29th of February This is the quest for the last word exotic hand cannon. It showcases some epic last word action That's for sure check out the trailer right now and watch until the very ends of people Did you guys witness that not only did we see the last word doing as it shouldn't absolutely destroy him Well, did you see the end every hero needs a villain and we see people foreign bullets from the phone hand cannon Something that was so destructive at one stage in PVP in destiny one It totally shaped the future of the franchise the phone was an absolute monster who remembers those trials days Everybody just sitting back with a phone two shots cross map would destroy. Yeah.  Don't forget the last word quest drops tomorrow 29th of February Hopefully ain't no time gated rubbish and we can get it straight away. That would be pretty cool But guys, let me know what you think about the phone returning down below in that comments section I hope you guys enjoyed the video if you did leaving a like really helps out if you are new around here and enjoy daily Destined to videos like guides top 5s gameplays reviews just about everything make sure you subscribe And if you never want to miss a video upload turn notifications on by hitting that bell button But again, thanks as always for stopping by and hopefully I will see you on that next one


What is going on everybody is Stas here welcome back to another video so in this video We're gonna be doing an overall market update looking at the Dow Jones the S&P 500 and the Nasdaq We're gonna be talking about two trades that I made today on the 7th of March and 2019 as well as taking a look at some other Stocks and ETFs that I personally see potential in over these next couple of weeks here in March And we're also gonna be talking about this whole Elon Musk situation that's going on right now with the rumors of him Possibly be suspended as the CEO of Tesla we're gonna be talking about that here in a couple of minutes But before we do hop into these topics of today's video for everybody out there that finds Valuing these videos the trading update videos the market update videos the personal finance the trading tips videos Feel free to go down below and hit that like button guys It really does support the growth of the channel and if you're new to the channel and new to the community Feel free to go down below to the description box and join our 100% free This core group chat as well as our 100% free Facebook group I guarantee you guys you will find value in those platforms 100% guarantee you that so let's talk about What's going on right now in the overall market starting off here with the spx so with about 17 minutes left Here in the market we can see the spx is down about 1% down about $26.20 the Dow Jones Industry industrial average tongue twister guys down about $230 down about 0.85% and the NASDAQ composite guys down a whopping $90 today so far down about 1.25% so it's looking like guys We're gonna end up closing the day today on a red day and for those of you guys that watched my video yesterday I was talking about how the overall markets, especially the spx have shown Indications of a further sell-off right we talked about how we got that double top a couple of days ago that we can see here On a closer term chart we can see the double top here Which was the first indication that we were selling off the second indication that we got a couple of days back as well Was the break below the 50 SMA support and the EMA that was the second and third Indications I guess you can say the the fourth indication that we got which is what we were looking for a couple of days ago Was the break below the support of this channel right here the uptrend channel that we were trading in over the past couple of Weeks pretty much right and what I was looking for today and what I talked about in yesterday's video Was the break below this 50 SMA support here on the 184-hour chart which would be the fourth indication that we're continuing to push down and that's exactly what we ended up Seeing today on the 7th of March with about a 1% push to the downside for the SPX So right now guys I'm sure you already can tell here from this chart here And of course if you've been doing your own technical analysis and research We are really selling off pretty hard in the SPX and the overall market So what am I watching now in terms of the SPX now that we've gotten about four Indications that we're pushing down the next indication. I want to see for further sell-off in the SPX Would be a break below this previous Resistance which is acting as a new support right now at about 2740 and for those of you guys that don't know whenever an ETF a stock an index or future is On an uptrend pattern is pushing up making higher highs like the SPX was here You know the points that we're pushing up to those are obviously going to be Resistance levels if we do end up breaking below them and of course if we're above them like we are right now They're going to be Support levels if we're pulling back down towards them if that makes any sense right and we can see right now We're pulling back down towards that old resistance, which again now is a new support level So we're testing this area. It seems like we're having some difficulty breaking below it here towards the market closed today We can see literally right at that point guys. No lie. Take a look 2739 We ended up bouncing here about an hour ago at 250 p.m. Eastern Standard Time And that happens to be literally right at that level 2739, you know Where we topped off back in the beginning of February in 2019 So this is the level that we're currently holding now and probably going to hold until the market closes here and about 13 minutes in the SPX and that's what I'm going to be watching for tomorrow morning during doing my futures analysis Doing, you know the pre-market analysis in terms of the three major indices here and of course looking at large cap stocks How are they performing are they selling off or some of the big name companies out there selling off heavily pre-market hours? Which would probably correlate to the futures of the major indices selling off, you know These are things we're going to be keeping an eye on Tomorrow morning to see where are we headed over the next couple of weeks in terms of the SPX? So my prediction guys, you know if we do end up breaking this level down here like I mentioned in yesterday's video We might be forming a head and shoulders pattern and we can see this would be the left shoulder in that scenario This would be the head and let's say we break this level tomorrow And then we start to see some pushback because at that point We're going to be very oversold in terms of the SPX So if we do end up pushing down tomorrow, maybe we see a day or two of pushback up next week That's going to look like a head and a shoulder pattern Right and for those of you guys that don't know about head and shoulder patterns Take a look deeper into that pattern. That's a very basic pattern that a lot of people out there Probably know but a lot of the beginners out there probably don't know and it's one of the patterns that We like to identify here in terms of our channel my channel here on youtube and our community You know again link down below the discord chat And you know, that's what I see is currently happening in terms of the SPX So keep an eye major level right here But as of right now all signs are pointing to more red in the s and p 500 now the dow Jones guys very similar Right, we're holding that old resistance at about 25400 as a new support level we're right at that level right now And just like the SPX guys, we had multiple multiple multiple Indications that we're selling off in the dow Jones if we take a look here on the 10 day 30 minute chart We can see that little resistance here at about 26200 dollars It wasn't really a double top formation like the SPX was actually let me go to that 20 day chart Well, you know, it wasn't really a double top. It was more of like A strong resistance here a couple of tops We can see one two three four different tops right around that 26 000 level of resistance And from there, you know, we got that first indication of the strong resistance meaning that we could be potentially selling off We got that sell off below the 50 sma and the ema which were both Support levels here on the 30 day 90 minute chart. We can clearly see that So that was two indications were selling off and obviously we broke below the support of that channel That we've been talking about over the past couple of videos and weeks honestly here on the channel Which would be the third indication and now today just like the SPX guys We ended up breaking that 50 sma support level on the 184 hour chart And again, like I mentioned about a minute ago, we're currently holding that older resistance as a new Support level. So what am I watching for the dow Jones very similar to the SPX? I want to see are we going to break the support level and sell off even further and from there We're going to be testing roughly about the 25 000 level Which would potentially be the next support we're heading to or we will be heading to you know in terms of the dow Jones But right now everything is pointing to red Everything is pointing to more potential selling in the overall markets here, especially with the dow Jones Now let's take a look at the nasdaq composite guys, which absolutely got obliterated today We can see it's falling even further from the beginning of this video just simply 10 minutes ago We can see from about 1.2 percent when we started off the video. We're down about almost 1.4 percent today in terms of the nasdaq we're down nearly 100 Dollars and we pretty much broke the entire uptrend pattern for the nasdaq We blew through the floor of that support level here on the 30 day 90 minute chart that we were trending above just simply two days ago We can clearly see we were at the support level for you know a couple of days here We can see it's a valid support level from the past back, you know from the beginning of february We held it once twice, you know three four five six seven eight nine a bunch of different times here And we clearly broke through that about yesterday and heading into today With the big nearly 100 point loss that we're currently seeing so right now guys, you know The nasdaq is looking like it's getting pretty pretty ugly Especially especially if we do end up breaking this 180 sma support level, which it does seem like we're still Holding above here towards the close of the market So tomorrow is going to be a very very big You know telling tale of where we're going to be headed over this next week because if we do end up breaking this critical support guys We're going to be headed back down to about 6,950 which would be the next support we're looking at since it was a previous resistance back in the middle of November so just keep an eye on these levels guys, but right now obviously all the indices, especially the nasdaq They're looking like falling knives with more potential selling Judging off of these technicals that we are seeing, you know in the major indices and that's what i'm really just seeing right now guys More red more red and i'm sure a lot of you guys know whenever the markets are red I'm trading tvix Which is exactly what I ended up trading today on the 7th of march In 2019 and for those of you guys that don't know tvix is my go to etf Whenever the markets are getting crushed or whenever the markets are just simply Down trending and selling off for the day, which is exactly what we ended up seeing today Obviously with the charts that we just saw, you know the spx the dow and the nasdaq Let's just take a look very quickly on a one day one minute basis They all sold off or one day one minute basis rather they all sold off pretty heavily today, especially in the morning Where I actually ended up trading tvix and for those of you guys that don't know tvix is an etf that trades Primarily based upon the spx the smp 500 and obviously whenever the spx the smp 500 is selling off tvix is going up in price so you guys can obviously see Where I ended up trading tvix if I traded it this morning I ended up popping in right on this big sell-off that we got from about 27 66 All the way down to about 27 42, which is about a 24 point sell-off And i'm sure a lot of you guys can imagine a 24 point sell-off in the spx that might have opened up a Six seven percent profit in tvix and you're exactly right because that's exactly what ended up happening from 32 Up to about 35 dollars actually no 34 and 60 cents that opened up a seven percent margin of profit in tvix and you don't really see charts like this all the time guys where it's literally straight up No pullbacks no consolidation. No stopping. This is literally a stock chart that went from 9 33 a.m At 32 dollars all the way to about 952 literally 20 minutes It took a seven percent move in 20 minutes with minimal minimal breaks minimal minimal consolidation points You can literally count one two here straight shoot straight shoot up chart here in terms of tvix And I know a lot of you guys have been following me for a while You know when i'm day trading i'm mostly aiming for a quick little one Two percent profit sure I could have got five percent six percent on tvix here But if I told you that I would be flat out lying because i'm more conservative guys I don't like to get as much profit per trade because a lot of times that I try and do that You know I end up getting bit in the butt and I do end up giving profit back to the markets Which is not what you want to do right you want to be able to be consistent be conservative You don't have to be conservative. You don't have to do exactly what I do Of course you do your own strategy whatever works for you But I'm just here telling you guys what I personally do and I'm more conservative and I feel comfortable Taking you know a one percent profit sometimes on a day trade maybe two percent And I know a lot of you guys have seen me take a three four percent profit sometimes But today specifically guys I literally got in and out within five six minutes on this tvix move And I took about a one point five percent profit and you can clearly see with the seven percent margin I was available 1.5 is pretty pretty conservative and that's exactly what I personally ended up doing Today right very simple so tvix was the day trade that I made today And I know a lot of you guys in the discord chat also traded tvix So if you did congratulations, you did very well today because tvix is still climbing at the close of the market right now We can see we're clearly up almost eight percent On this etf as of right now and another one that I actually took my profits on today Just to play it safe because I was already up nearly about I think like two percent or something was j and j And j and j is a stock that I've been holding now for about two three weeks I got in back here at about 135 135 50 And I've been simply holding this one, you know as a swing trade right and my goal was to sell at about $140 but today I actually saw J and j selling off pretty strongly and pretty heavily this morning as did a lot of stocks because the markets Were selling off and I kind of did panic not panic because I was already up I'm already up guys like I can show you guys right here from about 135 50 Up to about where we were this morning. I was already up a good amount about two three percent So I just wanted to lock in those profits while I did have them and potentially re-enter at a better price point Since we did see, you know, it's it's selling off very very strongly So I thought it was wise here to take my profits and I did take my profits at about $138 and 65 cents as I did see some very aggressive selling because I didn't want to lose You know a good amount of those gains that I did have simply by, you know, just holding through So what am I what am I going to do right now guys? I'm potentially going to re-enter into j and j if we do see a hold Above this 50 SMA support over these next couple of days of trading. So overall guys, that's what I ended up doing today I just took my profits on j and j about a two two point two percent Profit there and I ended up day trading Tvix for a nice quick in and out 1.3 1.4 Profit so that is what I did today Let me know down below in the comment section what you guys ended up doing in terms of your trading and now let's talk about What went down today with elan musk and tesla stock? Let's get into it So we all know by now tesla and elan musk have problems with the sec Right elan musk does not like the securities and exchange commission whatsoever And for those of you guys that have been following tesla tesla stock and just keeping up with the company Over the past couple of months you saw that a couple of months back in the middle of 2018 elan musk sent out a tweet that tesla will go private at $420 funding secured and pretty much this violates a lot of different laws with the sec because it can influence You know investors to push the stock price up and it just influences the stock price In general and since then obviously, you know elan musk came to you know an agreement with the sec He's going to have his tweets monitored There's going to be a lot of monitoring with him and the public in terms of communication Right and we saw a couple of weeks back elan musk and twitter back at it again with a bunch of more drama and him really just poking fun I think at the sec really just like you know, you know what I mean, right? I feel like he's just poking fun I feel like he's just trying to to bother them on purpose or something I know you guys relate and understand what i'm saying and you see the tweet up here on the screen right now And i'm reading it off of my phone This tweet on the 19th of february is what the sec is currently investigating and what the sec You know wants to really just get musk in trouble for Again, and we can see 4 000 cars being loaded in san francisco for europe This was before the march 1st trade deadline Which is obviously irrelevant now because it was pushed back But back towards the end of february just a couple of weeks ago You know tesla was trying to push as much of his cars, you know back to europe and over to china We saw all of those, you know big boats taking the cars over there to avoid, you know further You know, uh, what's it called tariffs on the cars because we all know elan musk and Trump and you know, not really elan musk, but trump and china They were he was going to raise the tariffs from china You know 10 to 25 and to avoid paying that musk was trying to send as much cars over there as possible Which doesn't make sense right and at the bottom of that tweet you can see here again tesla made zero cars in 2011 But will make around 500 000 cars in 2019 So just like the funding secured at 420 tweet This is a tweet that can influence investors out there to push the price of the stock up And this is obviously violating those terms that him and the sec came to a couple of months ago Which is why the sec is investigating him again guys. So I feel like elan musk right now Is just out of control right we obviously all know that this man is just out of control He does not care.  It's bringing unwanted attention to tesla as a company and and honestly Elan musk could be suspended as the tesla ceo Due to this because this is his second violation and under One year with the sec and for those of you guys especially those of you all in the stock market investors traders, whatever You know the sec is Is an organization that does you should not want to mess with them, right? You want to abide by their laws abide by their rules and really just play it out smoothly, right and elan musk He's doing the opposite right he likes to cause as much friction as possible He likes to piss off the sec and he just likes all of the drama So this is just the news right now guys, you know the tweet that I just showed you the investigation is going on And take it for what it is right elan musk he potentially could be suspended or this could blow over He might not get suspended, but they will get fined a hundred percent and they will have lawsuits no matter what I personally think so what do you guys think about this right? Is he going to get suspended what is going to happen? But in terms of the price of the stock tesla today We saw it actually went up to about 284 dollars and then we saw this news came out I forget did it come out like middle of the day today? It must have because at this point 283 dollars per share it tanked under nine dollars roughly about nine ten dollars per share In the matter of about from 12 p.m. Eastern standard to about three p.m Eastern standard in the matter of three hours tesla stock fell about three percent to the reaction of this news and actually guys, excuse me We're seeing some crazy unusual not really unusual But some crazy movement right now after market hours in terms of tesla stock Literally when I was recording this video in between the clips From the previous clip to this clip in this video this stock popped up Look at this green candlestick right here from 267 or 276 rather at the close all the way up to 283 So that was a big big big move in about one two minutes here 2.3 And now we're consolidating right here. So let me actually see what the live news is saying here if there's anything, um, you know new Not really seeing anything uh new here, but that's pretty cool, right? That's pretty cool to see the stock shot up all the way But anyway, what do you guys think about this? Please? Please? Please let me know the uh, you know Let me know down below in the comment section What you guys think and let's talk about very briefly what stocks need tfs I'm watching over these next couple of days and weeks here in march of 2019 And just to keep it very simple with you guys We're back in that state of the market where I'm kind of getting nervous to swing trade stocks again Especially with the overall market, especially the spx showing more potential signs of a sell-off and by this I mean, you know Just like back in october and november and december back in 2018 when we had this huge sell-off, you know, this wasn't a time To swing trade stocks and obviously the technicals aren't looking as bloody as this obviously It's very clear But this could be the beginning of more selling off Which scares me to buy and hold specific stocks as swing trades Which is primarily why I did end up selling off j&j today And yes, I'm still holding coca-cola with an average at about 45 dollars and I'm not too heavily into that position I have not yet to add more to that position But those are the only or really that's the only one that I'm holding right now in terms of swing trading So in terms of you know, what I'm watching guys over these next couple of days I'm really going to be just looking at some inverse ETFs And market ETFs that trade based upon the overall movement of the market like tvix If we continue to sell off your guys, you know, I'm just going to be trading in and out of tvix Every single day like I was in between, you know, october october and you know, december of 2018 Like I'm sure a lot of you guys already know who are watching the channel back during these time periods I was literally selling or trading it rather it feels like every single day of the week I was trading in and out of tvix. So if the markets continue to sell off tomorrow You know, this gonna that's going to open up a ton of margin in terms of tvix And especially next week, let's say the markets continue to sell off. They continue to sell off This is going to push up and open up a ton a ton of opportunity In terms of day trading so tvix guys actually the go-to number one ETF right now That I am watching over these next couple of days. Of course some other stocks, you know, including tesla Tesla's a stock that doesn't actually do too poorly when the markets are selling off, believe it or not, right? We can see back in, you know, the october december days tesla stock actually did very well We can see from 260 up to about $375 that's where it went while the market as a whole was selling off Am I saying that tesla stock is you know a stock that's uh, you know sell-off proof You know when the markets are selling off, absolutely not but just judging off the previous You know market movement That is what I see and if the markets do end up selling off further and I noticed tesla's pushing up You know this could be an opportunity for me to hop into tesla as a potential day trade Maybe even as a couple of days, you know as a swing trade if the technicals are looking Good and as of right now guys, you know, we're holding above that 275 support very nicely And honestly if we start to push back up into the 280s Mid 280s, maybe the 290s That's going to be a good sign that we're slowly heading back up to the top resistance portion of this channel that we notice here on tesla stock So i'm also watching cron here ticker symbol c r o n we noticed the margin of profit opened up in cron From the sell-off at about 24 dollars down to about 22 dollars That opened up a nice 10 margin and we're still holding above that 50 sma nicely So i would like to see a potential pop up here so i can profit on the upside here in terms of ticker symbol c r o n And uh guys when i'm telling you that's all i'm really watching right now in terms of aftermarket for tomorrow That is what i'm watching really just cron and tvix because i've had the experience when the markets are selling off I do very well day trading tvix and i'm just keeping it real with you guys So that's what i'm looking at in terms of tomorrow i'm sure they'll be there will be more opportunities once The futures open up tomorrow morning We get to see what the markets are likely going to open up and of course we're going to be seeing You know large cap stock movements and other stock movement here in my watch list And that's going to open up even more opportunities, but at the time right now at the end of the of the market You know, that's what i'm personally watching for tomorrow And if we take a look at some other charts, you know, none of these charts are screaming You know as a buy right now, right? We can see walmart is not looking too well You know didn't hold that trend that we wanted it to square You know, I might as well just take this one off my watch list This one's looking pretty bearish right now, especially if it breaks the 180 sma You know another one we called out yesterday spotify spotify is not looking too well Not looking too great right now. So until these charts, you know start to open up with some upwards movement I'm not really going to be looking to hop into them, right? We can see cat here sold off pretty heavily You know billy's not looking too great either. So I want to see, you know, some push to the upside in these stocks before Trading them. That's just what i'm looking at right now. So I hope you guys enjoy this video Let me know down below in the comment section what you guys ended up trading today What stocks you're watching I would love to know if you enjoyed this video Feel free to hit that like button leave a comment and subscribe Follow me on instagram as well as on twitter all of those are linked down below and don't forget get into our 100 free discord and facebook group. Those are both linked down below in the description box I'll catch you all in the next video. Thanks again for watching. Peace out